[mediaqueries-4] order of prefixes
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- css
- Domain
- documentation
Research direction
Read the Media Queries Level 4 range-feature section and the CSS2 vendor-keyword reference linked in the issue, then compare them with the Compat specification's explicit handling of -webkit-device-pixel-ratio. Determine what ordering rule the specification should define and document the chosen behavior in the relevant draft, with the result consistent with existing browser implementations.
Written by the indexing model from the issue text.
Description
https://drafts.csswg.org/mediaqueries-4/#mq-min-max defines min/max prefixes for range features.
https://www.w3.org/TR/CSS2/syndata.html#vendor-keywords reserves prefixes for vendor-specific extensions, at least for keywords and property names.
While admitting that media features aren't keywords or property names, the reality is that there are prefixed ones used in the wild (e.g., -webkit-device-pixel-ratio), and we should define somehow how prefixes get applied to device-pixel-ratio.
Should we have min--webkit-device-pixel-ratio or -webkit-min-device-pixel-ratio?
Clearly, the latter is the one that is implemented in every major browser engine, but there's nothing that actually says the prefixes should be applied in that order, and the Compat spec feels a need to make this explicit: https://compat.spec.whatwg.org/#css-media-queries-webkit-device-pixel-ratio
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 24
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from w3c/csswg-drafts
-
Agenda+ css-sizing-4 css-values-5
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
w3c/csswg-drafts#14502 · 1 reaction ·
-
css-values-5 editorial Needs Edits
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
w3c/csswg-drafts#14498 · 2 comments ·
-
css-overflow-4 topic: line-clamp
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
w3c/csswg-drafts#14485 · 1 comment ·
-
Administrative Tracker css-values-4
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
w3c/csswg-drafts#14482 · 4 comments · 1 reaction ·
-
css-values-5 Needs Edits
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
w3c/csswg-drafts#14466 ·
All issues in w3c/csswg-drafts
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bancolombia/sentinel#22 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
objectionary/hone-maven-plugin#1061 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
redhat-developer/rhdh-plugins#4887 · 2 comments ·