Created attachment 772751 [details] Extra space with Australis @2.0 Scaling On windows with Australis, when DPI scaling is set to 2 (via layout.css.devPixelsPerPx=2), there appears to be too much space to the right of the tabstrip (below the windows controls), and it seems there's enough space there for the buttons to reach the right-edge of the window. I'm not sure if it's by design or not, since with 1.0 scaling there isn't enough space below the windows controls. This could be related to the fact that with Australis the window "title" is shorter than with the current there (bug 887397 ?). In any case, this bug is about making sure that Australis behaves as expected also with supported DPI scaling (wrt tabstrip space, title height, etc).
What happens on m-c with such scaling? Generally speaking, hidpi-on-Windows is an only just starting to show up on the radar as a configuration we're "supporting", so unless we're regressing what m-c looks like in an egregious way, this isn't something I'd track for Australis.
(In reply to Justin Dolske [:Dolske] from comment #1) > What happens on m-c with such scaling? Not perfect either, but the future is Australis, so m-c matters less IMO. Specifically in m-c, in windowed mode: the tabs hide the bottom part of the Firefox button. In maximized mode: we could probably reduce the space a bit to the right of the tabstrip. > Generally speaking, hidpi-on-Windows is an only just starting to show up on > the radar as a configuration we're "supporting", so unless we're regressing > what m-c looks like in an egregious way, this isn't something I'd track for > Australis. IMO hidpi is the next(/current?) big thing, and it's already out there. 10" tablets with 1080 displays are here, and I'd imagine many will setup scaling on windows. As for how bad the issues are, it's a judgment call, and I didn't claim the specific issue I pointed at should be a blocker. This bug is about making sure that hidpi cases are not neglected while working on and testing Australis.
As an OS X Retina user, I totally agree that hidpi is the next big thing. :) Let's call this a meta bug -- we'd certainly take patches to fix issues, and shouldn't ship with grossly worse hidpi support, but pixel polish for this first round of Australis on hidpi is explicitly out of scope. It's already big and late. :(
Aren't we also scaling our borders, gradients, favicons, which are all implemented as bitmaps? Blurry UI seems like a significant regression.