Re: [csswg-drafts] [css-syntax] Give up on <urange> production? (#8835)

What is expected to move this issue forward?

Firefox fails the [tests on WPT](https://wpt.fyi/results/css/css-syntax/urange-parsing.html?label=master&label=experimental&aligned) because they use `CSSFontFaceRule.style`. Using a style sheet, the results are identical to those of Chromium based browsers, and fail tests that still expect comments to be accepted within the range. 

Do the tests need to be edited?

The [`unicode-range`](https://drafts.csswg.org/css-fonts-4/#descdef-font-face-unicode-range) descriptor is defined with `<urange>#` but `<urange>` is now undefined. 

Would it be ok to update its definition to `<unicode-range-token>#`?

CSS Fonts 4 defines these two requirements (applied by all browsers):

  - the start and end values must be between 0 and 10FFFF inclusive
  - the start value must be lower than or equal to the end value

The text says "*it must [satisfy these requirements]*" but does not says "*otherwise the descriptor is invalid*" or "*otherwise the descriptor is ignored*". I guess it should be invalid, but it can probably be clarified.

Lastly. This probably deserves a separate issue. `CSSFontFaceDescriptors.setProperty('unicode-range', ...)` does not involve [*consume a declaration*](https://drafts.csswg.org/css-syntax-3/#consume-a-declaration), therefore the tokenizer mode cannot be switched.

  > Otherwise, if `decl`’s name is an ASCII case-insensitive match for "unicode-range", consume the value of a unicode-range descriptor [...]

-- 
GitHub Notification of comment by cdoublev
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8835#issuecomment-2489475071 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 20 November 2024 20:22:38 UTC