Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Treat component failures leniently in @font-face src: parsing #40620

Closed
wants to merge 1 commit into from

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

Adapt font-face src: parsing behavior to more leniently accept a src:
line that has parse errors in an individual component. Part of Interop
2023 in the font feature detection and palettes category [1].

Also return serialized values in lowercase to match CSSOM spec.

After CSS WG resolution [1] and updated spec text [2] individually
failing src: line components for incorrect format() or tech(), or other
parse failures per component should not lead to dropping the whole src:
line, but only reject the individual component.

Implement checks for component sanity and on failure, skip to next comma
or end.

[1] https://wpt.fyi/results/css/css-fonts/parsing?q=label%3Ainterop-2023-fonts
[1] w3c/csswg-drafts#6340
[2] https://drafts.csswg.org/css-fonts-4/#font-face-src-parsing

Fixed: 1398933, 857226
Change-Id: Ib94f745fb8b453e21fd981973c29dccb4b722439
Reviewed-on: https://chromium-review.googlesource.com/4624052
WPT-Export-Revision: 7d63f5ec4d7c75f0b2ffa2befa6ed70edcda9f48

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

Adapt font-face src: parsing behavior to more leniently accept a src:
line that has parse errors in an individual component. Part of Interop
2023 in the font feature detection and palettes category [1].

Also return serialized values in lowercase to match CSSOM spec.

After CSS WG resolution [1] and updated spec text [2] individually
failing src: line components for incorrect format() or tech(), or other
parse failures per component should not lead to dropping the whole src:
line, but only reject the individual component.

Implement checks for component sanity and on failure, skip to next comma
or end.

[1] https://wpt.fyi/results/css/css-fonts/parsing?q=label%3Ainterop-2023-fonts
[1] w3c/csswg-drafts#6340
[2] https://drafts.csswg.org/css-fonts-4/#font-face-src-parsing

Fixed: 1398933, 857226
Change-Id: Ib94f745fb8b453e21fd981973c29dccb4b722439
@chromium-wpt-export-bot
Copy link
Collaborator Author

Close this PR because the Chromium CL does not have exportable changes.

@chromium-wpt-export-bot chromium-wpt-export-bot deleted the chromium-export-cl-4624052 branch June 21, 2023 11:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants