Stowage/ladybird
2
0
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2025-10-19 07:33:20 +00:00
Code Issues Projects Releases Packages Wiki Activity
ladybird/Tests/LibWeb/Text/expected/css/CSSStyleDeclaration-has-indexed-property-getter.txt

303 lines
6.6 KiB
Text
Raw Normal View History

LibWeb: Make CSSStyleDeclaration a legacy platform object with indices CSSStyleDeclaration has an indexed property getter, which returns properties associated with the object in the order they were specified in.
2024-11-14 17:05:56 +00:00
All properties associated with getComputedStyle(document.body):
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
[
"-webkit-text-fill-color",
"accent-color",
"border-collapse",
"border-spacing",
"caption-side",
"caret-color",
"clip-rule",
"color",
LibWeb: Implement the `color-interpolation` property for SVG gradients This changes the operating color space for gradient `<linearGradient>` and `<radialGradient>` elements.
2025-08-15 23:53:15 +01:00
"color-interpolation",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"color-scheme",
"cursor",
"direction",
LibWeb/CSS: Implement the `empty-cells` property This property sets whether table borders and backgrounds are painted if a given table cell has no visible content.
2025-06-18 12:28:18 +01:00
"empty-cells",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"fill",
"fill-opacity",
"fill-rule",
"font-family",
"font-feature-settings",
LibWeb/CSS: Implement the `font-kerning` property This sets whether the kerning information stored on the current font is used.
2025-06-22 18:59:42 +01:00
"font-kerning",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"font-language-override",
"font-size",
"font-style",
"font-variant-alternates",
"font-variant-caps",
"font-variant-east-asian",
"font-variant-emoji",
"font-variant-ligatures",
"font-variant-numeric",
"font-variant-position",
"font-variation-settings",
"font-weight",
"font-width",
"image-rendering",
"letter-spacing",
"line-height",
"list-style-image",
"list-style-position",
"list-style-type",
"math-depth",
"math-shift",
"math-style",
LibWeb: Parse `orphans` CSS property
2025-09-27 02:43:23 +12:00
"orphans",
LibWeb: Treat `word-wrap` as an alias for `overflow-wrap`
2025-09-27 19:52:51 +01:00
"overflow-wrap",
LibWeb/CSS: Parse the `paint-order` property
2025-08-24 15:00:53 +01:00
"paint-order",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"pointer-events",
"quotes",
LibWeb: Parse the `shape-rendering` property
2025-08-16 17:48:30 +01:00
"shape-rendering",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"stroke",
"stroke-dasharray",
"stroke-dashoffset",
"stroke-linecap",
"stroke-linejoin",
"stroke-miterlimit",
"stroke-opacity",
"stroke-width",
"tab-size",
"text-align",
"text-anchor",
"text-decoration-line",
"text-indent",
"text-justify",
LibWeb/CSS: Add the `text-rendering` property
2025-06-27 07:03:05 +01:00
"text-rendering",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"text-shadow",
"text-transform",
LibWeb: Parse and compute `text-underline-offset` property
2025-09-11 22:00:19 +12:00
"text-underline-offset",
LibWeb: Parse `text-underline-position` property This introduces the `TextUnderlinePositionStyleValue` class, it is possible to represent `text-underline-position` as a `StyleValueList` but would have required ugly workarounds for either serialization or in `ComputedProperties::text_underline_position`
2025-09-13 19:27:52 +12:00
"text-underline-position",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"text-wrap-mode",
LibWeb: Implement `text-wrap-style` CSS property
2025-05-31 20:31:07 +12:00
"text-wrap-style",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"visibility",
"white-space-collapse",
LibWeb: Parse `widows` CSS property
2025-09-27 02:44:54 +12:00
"widows",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"word-break",
"word-spacing",
"writing-mode",
"align-content",
"align-items",
"align-self",
LibWeb: Parse the `anchor-name` property
2025-10-02 21:14:19 +01:00
"anchor-name",
LibWeb: Parse the `anchor-scope` property
2025-10-01 22:08:06 +01:00
"anchor-scope",
LibWeb: Implement the `animation-composition` property
2025-09-18 19:59:33 +01:00
"animation-composition",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"animation-delay",
"animation-direction",
"animation-duration",
"animation-fill-mode",
"animation-iteration-count",
"animation-name",
"animation-play-state",
"animation-timing-function",
"appearance",
"aspect-ratio",
"backdrop-filter",
"background-attachment",
"background-blend-mode",
"background-clip",
"background-color",
"background-image",
"background-origin",
"background-position-x",
"background-position-y",
"background-repeat",
"background-size",
"block-size",
"border-block-end-color",
"border-block-end-style",
"border-block-end-width",
"border-block-start-color",
"border-block-start-style",
"border-block-start-width",
"border-bottom-color",
"border-bottom-left-radius",
"border-bottom-right-radius",
"border-bottom-style",
"border-bottom-width",
LibWeb: Add `border-*-radius` logical properties
2025-06-30 20:33:17 +01:00
"border-end-end-radius",
"border-end-start-radius",
LibWeb: Parse the `border-image-outset` property
2025-06-10 23:54:48 +01:00
"border-image-outset",
LibWeb: Parse the `border-image-repeat` property
2025-06-11 00:08:37 +01:00
"border-image-repeat",
LibWeb: Parse the `border-image-slice` property
2025-06-10 16:58:54 +01:00
"border-image-slice",
LibWeb: Parse the `border-image-source` property
2025-06-10 05:29:50 +01:00
"border-image-source",
LibWeb: Parse the `border-image-slice` property
2025-06-10 16:58:54 +01:00
"border-image-width",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"border-inline-end-color",
"border-inline-end-style",
"border-inline-end-width",
"border-inline-start-color",
"border-inline-start-style",
"border-inline-start-width",
"border-left-color",
"border-left-style",
"border-left-width",
"border-right-color",
"border-right-style",
"border-right-width",
LibWeb: Add `border-*-radius` logical properties
2025-06-30 20:33:17 +01:00
"border-start-end-radius",
"border-start-start-radius",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"border-top-color",
"border-top-left-radius",
"border-top-right-radius",
"border-top-style",
"border-top-width",
"bottom",
"box-shadow",
"box-sizing",
"clear",
"clip",
"clip-path",
"column-count",
"column-gap",
LibWeb: Add CSS column-height property
2025-09-04 21:50:06 +02:00
"column-height",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"column-span",
"column-width",
"contain",
LibWeb/CSS: Parse the container-type property This applies size, inline-size, and style containment in some cases. There are other WPT tests for that, but we seem to not implement enough of containment for this to have an effect so I've not imported those. Gets us 35 WPT subtests.
2025-09-30 14:48:55 +01:00
"container-type",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"content",
"content-visibility",
LibWeb: Parse `corner-*-shape` physical longhands
2025-10-08 22:43:27 +13:00
"corner-bottom-left-shape",
"corner-bottom-right-shape",
LibWeb: Support `corner-*-shape` logical properties
2025-10-09 00:56:35 +13:00
"corner-end-end-shape",
"corner-end-start-shape",
"corner-start-end-shape",
"corner-start-start-shape",
LibWeb: Parse `corner-*-shape` physical longhands
2025-10-08 22:43:27 +13:00
"corner-top-left-shape",
"corner-top-right-shape",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"counter-increment",
"counter-reset",
"counter-set",
"cx",
"cy",
"display",
"filter",
"flex-basis",
"flex-direction",
"flex-grow",
"flex-shrink",
"flex-wrap",
"float",
LibWeb/SVG: Add FEFloodElement
2025-07-06 21:48:55 +02:00
"flood-color",
"flood-opacity",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"grid-auto-columns",
"grid-auto-flow",
"grid-auto-rows",
"grid-column-end",
"grid-column-start",
"grid-row-end",
"grid-row-start",
"grid-template-areas",
"grid-template-columns",
"grid-template-rows",
"height",
"inline-size",
"inset-block-end",
"inset-block-start",
"inset-inline-end",
"inset-inline-start",
"isolation",
"justify-content",
"justify-items",
"justify-self",
"left",
"margin-block-end",
"margin-block-start",
"margin-bottom",
"margin-inline-end",
"margin-inline-start",
"margin-left",
"margin-right",
"margin-top",
LibWeb/CSS: Parse mask-clip property
2025-07-18 20:36:12 +02:00
"mask-clip",
LibWeb/CSS: Parse mask-composite property
2025-07-18 20:36:06 +02:00
"mask-composite",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"mask-image",
LibWeb/CSS: Parse mask-mode property
2025-07-18 20:36:07 +02:00
"mask-mode",
LibWeb/CSS: Parse mask-origin property
2025-07-18 20:36:11 +02:00
"mask-origin",
LibWeb/CSS: Parse mask-position property
2025-07-18 20:36:08 +02:00
"mask-position",
LibWeb/CSS: Parse mask-repeat property
2025-07-18 20:36:10 +02:00
"mask-repeat",
LibWeb/CSS: Parse mask-size property
2025-07-18 20:36:11 +02:00
"mask-size",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"mask-type",
"max-block-size",
"max-height",
"max-inline-size",
"max-width",
"min-block-size",
"min-height",
"min-inline-size",
"min-width",
"mix-blend-mode",
"object-fit",
"object-position",
"opacity",
"order",
"outline-color",
"outline-offset",
"outline-style",
"outline-width",
LibWeb: Add the `overflow-block` property
2025-09-18 21:37:46 +01:00
"overflow-block",
LibWeb: Add the `overflow-inline` property
2025-09-18 21:40:27 +01:00
"overflow-inline",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"overflow-x",
"overflow-y",
"padding-block-end",
"padding-block-start",
"padding-bottom",
"padding-inline-end",
"padding-inline-start",
"padding-left",
"padding-right",
"padding-top",
"position",
LibWeb: Parse the `position-anchor` property
2025-10-01 17:07:01 +01:00
"position-anchor",
LibWeb: Parse the `position-area` property
2025-09-28 23:10:51 +01:00
"position-area",
LibWeb: Parse the `position-try-fallbacks` property
2025-10-01 19:04:10 +01:00
"position-try-fallbacks",
LibWeb: Parse the `position-try-order` property
2025-10-01 20:49:21 +01:00
"position-try-order",
LibWeb: Parse the `position-visibility` value
2025-10-01 21:52:23 +01:00
"position-visibility",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"r",
"right",
"rotate",
"row-gap",
"rx",
"ry",
"scale",
LibWeb/CSS: Implement the `scrollbar-color` property This allows the user to set the scrollbar thumb and track colors.
2025-05-26 22:36:12 +01:00
"scrollbar-color",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"scrollbar-gutter",
"scrollbar-width",
LibWeb: Parse the `shape-image-threshold` property
2025-10-17 02:54:47 +13:00
"shape-image-threshold",
LibWeb: Parse the `shape-margin` property
2025-10-17 03:28:07 +13:00
"shape-margin",
LibWeb: Parse the `shape-outside` property
2025-10-17 00:49:27 +13:00
"shape-outside",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"stop-color",
"stop-opacity",
"table-layout",
"text-decoration-color",
"text-decoration-style",
"text-decoration-thickness",
"text-overflow",
"top",
"touch-action",
"transform",
"transform-box",
"transform-origin",
"transition-behavior",
"transition-delay",
"transition-duration",
"transition-property",
"transition-timing-function",
"translate",
"unicode-bidi",
"user-select",
"vertical-align",
"view-transition-name",
"white-space-trim",
"width",
LibWeb: Parse the `will-change` property This property provides a hint to the rendering engine about properties that are likely to change in the near future, allowing for early optimizations to be applied.
2025-08-16 08:39:18 +01:00
"will-change",
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
"x",
"y",
"z-index"
]
LibWeb: Make CSSStyleDeclaration a legacy platform object with indices CSSStyleDeclaration has an indexed property getter, which returns properties associated with the object in the order they were specified in.
2024-11-14 17:05:56 +00:00
All properties associated with document.body.style by default:
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
[]
LibWeb: Make CSSStyleDeclaration a legacy platform object with indices CSSStyleDeclaration has an indexed property getter, which returns properties associated with the object in the order they were specified in.
2024-11-14 17:05:56 +00:00
All properties associated with document.body.style after setting some properties:
Tests/LibWeb: Print properties without indexes The test CSSStyleDeclaration-has-indexed-property-getter is a frequent source of merge conflicts between PRs that are adding to or otherwise modifying the list of supported CSS properties. This is primarily because the test prints out a numeric index of each property along with the property. As far as I can tell the indexes are inconsequential for what the test is trying to verify. So lets modify the printout to only contain the properties without indexes.
2025-06-01 19:32:24 +02:00
[
"display",
"background-color",
"font-size"
]
Reference in a new issue Copy permalink