Closed
Bug 765914
Opened 12 years ago
Closed 12 years ago
-moz-device-pixel-ratio misreported as 1.0 instead of 2.0 on Mac HiDPI display
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: brion, Unassigned)
Details
Attachments
(1 file)
1.08 KB,
text/html
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/16.0 Firefox/16.0a1 Build ID: 20120618030531 Steps to reproduce: Media queries using -moz-device-pixel-ratio or min--moz-device-pixel-ratio report the -moz-device-pixel-ratio value as 1.0 when running on a HiDPI screen, which should report a ratio of 2.0 (MacBook Pro with Retina display). (Note that this is on a nightly with layers acceleration disabled, as per notes on bug 674373.) Run the attached HTML file with a little scripting to check media queries. Actual results: Firefox nightly shows output: "-device-pixel-ratio is 1.0 or higher." indicating that -moz-device-pixel-ratio is 1 or higher but not higher than 1.5. Expected results: Safari and Chrome Canary build show expected output: "-device-pixel-ratio is 1.0 or higher. 1.5 or higher. 2.0 or higher." indicating that -webkit-device-pixel-ratio is 2 or higher but not higher than 3.
Reporter | ||
Updated•12 years ago
|
Attachment #634179 -
Attachment mime type: text/plain → text/html
Are we actually displaying at 2 CSS pixels per device pixel, and reporting 1, or are we displaying incorrectly too?
Reporter | ||
Comment 2•12 years ago
|
||
When I filed this, nightlies were running at high resolution when gfx acceleration was off, but changes to the painting code are running everything through low-resolution buffers now. So hopefully once everything's fixed to knowingly do high-res rendering through the whole pipeline, that should fix this...
Reporter | ||
Comment 3•12 years ago
|
||
Sample file seems to work as expected using Jonathan Kew's test build from bug 674373 comment 116. Yay!
Reporter | ||
Comment 4•12 years ago
|
||
This now works as expected on nightly since bug 674373 landed.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•