LibWeb: Change iterable<T> declaration order to match specifications

This commit is contained in:
Tim Ledbetter 2025-09-02 07:30:13 +01:00 committed by Sam Atkins
commit 5ce518f493
Notes: github-actions[bot] 2025-09-02 09:42:43 +00:00
2 changed files with 2 additions and 5 deletions

View file

@ -3,9 +3,7 @@
// https://drafts.css-houdini.org/css-typed-om-1/#cssnumericarray
[Exposed=(Window, Worker, PaintWorklet, LayoutWorklet)]
interface CSSNumericArray {
iterable<CSSNumericValue>;
readonly attribute unsigned long length;
getter CSSNumericValue (unsigned long index);
// FIXME: Different order than the spec, because IDLParser requires that this comes after the indexed property getter.
iterable<CSSNumericValue>;
};

View file

@ -5,11 +5,10 @@
[Exposed=(Window, Worker, PaintWorklet, LayoutWorklet)]
interface CSSUnparsedValue : CSSStyleValue {
constructor(sequence<CSSUnparsedSegment> members);
iterable<CSSUnparsedSegment>;
readonly attribute unsigned long length;
getter CSSUnparsedSegment (unsigned long index);
setter undefined (unsigned long index, CSSUnparsedSegment val);
// FIXME: Different order from the spec, because our IDL parser needs the indexed getter to be defined already.
iterable<CSSUnparsedSegment>;
};
// https://drafts.css-houdini.org/css-typed-om-1/#typedefdef-cssunparsedsegment