100861 2012-10-31 07:49:03 -0700 [chromium] Enable RESOLUTION_MEDIA_QUERY 2013-04-09 17:07:32 -0700 1 1 1 Unclassified WebKit CSS 528+ (Nightly build) Unspecified Unspecified RESOLVED WONTFIX WebExposed P2 Normal --- 99077 100865 1 rbyers rbyers johnme kenneth peter syoichi tabatkins oldest_to_newest 755297 0 rbyers 2012-10-31 07:49:03 -0700 Kenneth recently landed support for 'resolution' media queries and dppx units (bug 99077). I think we should enable it in chromium. 755300 1 peter 2012-10-31 07:52:20 -0700 We'll need ENABLE_CSS_IMAGE_RESOLUTION as well as it depends on that. I do completely concur for Android, but johnme@ has some concerns regarding the units we'd expose. 755303 2 rbyers 2012-10-31 07:57:04 -0700 (In reply to comment #1) > We'll need ENABLE_CSS_IMAGE_RESOLUTION as well as it depends on that. Are you sure? From the code it looked to me like it was perhaps designed to work without it. Anyway I will give it a try sometime soon (just some higher priority things in my queue first). > I do completely concur for Android, but johnme@ has some concerns regarding the units we'd expose. Great, let's discuss any concerns. Tab has been working on the spec, so I hope he's already been made aware of any concerns chromium folks have with it. 755312 3 peter 2012-10-31 08:04:16 -0700 (In reply to comment #2) > Are you sure? From the code it looked to me like it was perhaps designed to work without it. Anyway I will give it a try sometime soon (just some higher priority things in my queue first). I should read patches more carefully :-). You're right, thanks! 755318 4 kenneth 2012-10-31 08:16:33 -0700 Be aware that Chromium needs to stop forwarding the actual device dpi to the screen.vertical|horizontalDPI methods. 755387 5 johnme 2012-10-31 09:44:58 -0700 (In reply to comment #2) > (In reply to comment #1) > > I do completely concur for Android, but johnme@ has some concerns regarding the units we'd expose. > > Great, let's discuss any concerns. Tab has been working on the spec, so I hope he's already been made aware of any concerns chromium folks have with it. I filed bug 100865 about this. (In reply to comment #4) > Be aware that Chromium needs to stop forwarding the actual device dpi to the screen.vertical|horizontalDPI methods. Why do we need to stop this? And what should we do instead? 755446 6 kenneth 2012-10-31 10:34:26 -0700 (In reply to comment #5) > (In reply to comment #2) > > (In reply to comment #1) > > > I do completely concur for Android, but johnme@ has some concerns regarding the units we'd expose. > > > > Great, let's discuss any concerns. Tab has been working on the spec, so I hope he's already been made aware of any concerns chromium folks have with it. > > I filed bug 100865 about this. > > (In reply to comment #4) > > Be aware that Chromium needs to stop forwarding the actual device dpi to the screen.vertical|horizontalDPI methods. > > Why do we need to stop this? And what should we do instead? As far as I can tell you are not using it for anything (via that api) and the values are also not exposed to the web content (not declared in the idl). So I don't think you need to do anything instead. 872522 7 schenney 2013-04-09 17:07:32 -0700 Marked LayoutTest bugs, bugs with Chromium IDs, and some others as WontFix. Test failure bugs still are trackable via TestExpectations or disabled unit tests.