-
Notifications
You must be signed in to change notification settings - Fork 677
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
[css-values-4] Canonical <resolution> unit #2631
Labels
css-values-4
Current Work
Comments
Whoops, this is a duplicate of #2241. |
yisibl
added a commit
to yisibl/caniuse
that referenced
this issue
Jul 17, 2022
yisibl
added a commit
to yisibl/caniuse
that referenced
this issue
Jul 17, 2022
yisibl
added a commit
to yisibl/caniuse
that referenced
this issue
Jul 17, 2022
Fyrd
pushed a commit
to Fyrd/caniuse
that referenced
this issue
Jul 21, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Due to WebKit shipping some things using
x
as a<resolution>
unit, we added it to<resolution>
officially in Values 4. When adding it, I chose to setx
as the canonical unit for the type, as WebKit's additions seemed to be the main use for the type, and it seemed like preserving them as serializing withx
was important.Chrome is planning on finally actually implementing this - accepting
x
in the MQs that take<resolution>
, and accepting other<resolution>
units in an (unprefixed)image-set()
and<img srcset>
. The question that arises is thus whetherx
is really the best canonical unit to use or not, considering that other browsers don't yet implementx
, or whether we should change it todppx
.The text was updated successfully, but these errors were encountered: