commit | 3991e3a5d232e686c733f9f1bea8e3ed7d29550e | [log] [tgz] |
---|---|---|
author | Anders Hartvoll Ruud <andruud@chromium.org> | Sun May 15 20:35:06 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sun May 15 20:35:06 2022 |
tree | 8f3d47b20b5324f3152434a3ca58fc016ea94b17 | |
parent | 147cd2201c06760aa366daf74c03883948d20710 [diff] |
[mq-4] Enable CSSMediaQueries4 for stable This requires substantial WPT adjustments, since unknown parts of media queries now parse as <general-enclosed> [1] instead of becoming "not all". test_media_queries.html: - Deduplicate lazy evaluation of string templates. - Check that expressions are known or unknown instead of checking if they parsed. - Add new tests for "not", nesting, or, and missing forms of <mf-range> [2]. Other WPTs changed in this CL all use matchmedia-utils.js: - Check that queries are known or unknown instead of checking if they parsed. - Don't list the same test examples twice. Instead just require that known/unknown queries also parse successfully using both JS and CSS. Tests for the "sizes" attribute seemed to believe that (!) is not valid for <general-enclosed> (but it is). Changed to (]), which is not valid. [1] https://drafts.csswg.org/mediaqueries-4/#typedef-general-enclosed [2] https://drafts.csswg.org/mediaqueries-4/#typedef-mf-range I2S: https://groups.google.com/a/chromium.org/g/blink-dev/c/E4Vd7w70OsU Change-Id: I08243ed885ae523953f288b38a9ff4bb05370508 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3634678 Reviewed-by: David Baron <dbaron@chromium.org> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/main@{#1003559}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.