Closed
Bug 1324307
Opened 8 years ago
Closed 3 years ago
Ensure that -moz-device-pixel-ratio behavior matches -webkit-device-pixel-ratio
Categories
(Core :: CSS Parsing and Computation, defect, P3)
Core
CSS Parsing and Computation
Tracking
()
People
(Reporter: wisniewskit, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: dev-doc-needed, Whiteboard: [webcompat] [stylo])
As per recent CSSWG discussion[1],
>- Apple is considering changing webkit's behavior to align with the spec and other implementations,
>and make page zoom affect resolution. If they decide against in, they should file a bug against the spec.
>
>- If Apple changes their implementation of resolution as discussed in the previous point, they are
>unsure whether to keep -webkit-device-pixel-ratio a strict alias of resolution, or have it preserve
>the historical behavior, but lean towards the later one. If they decide that these should not be
>strict aliases, they should file a bug against the spec, which defines them to be.
Since we now alias -moz-device-pixel-ratio as -webkit-device-pixel-ratio (as of v45 for the WhatWG Compatibility Standard), we should ensure that it matches whatever behavior WebKit goes with.
[1] https://github.com/w3c/csswg-drafts/issues/417
Reporter | ||
Updated•8 years ago
|
Whiteboard: [webcompat]
Updated•8 years ago
|
Keywords: dev-doc-needed
Updated•8 years ago
|
Whiteboard: [webcompat] → [webcompat] [stylo]
Updated•7 years ago
|
Priority: -- → P3
Comment 1•6 years ago
|
||
Migrating Webcompat whiteboard priorities to project flags. See bug 1547409.
Webcompat Priority: --- → ?
Comment 2•6 years ago
|
||
See bug 1547409. Migrating whiteboard priority tags to program flags.
Updated•5 years ago
|
Webcompat Priority: ? → revisit
Comment 3•3 years ago
|
||
They evaluate using the same exact function: https://searchfox.org/mozilla-central/rev/763b888847ac7291248b62ef3ab99da6ba2332d6/servo/components/style/gecko/media_features.rs#732-752
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•