© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
(In reply to Stefan Seidel from comment #31)
> (In reply to Karl Tomlinson (ni?:karlt) from comment #28)
> > And the Linux UI is already following the Windows behavior at dpi scale
> > factors of 1.25. Text is scaled and images are not, because that is the
> > right thing to do at 1.25. Firefox UI images may be scaled by 1.25 on WINNT
> > but that would be a bug.
>
> No, on Windows, *everything* is scaled as defined by the Windows font scale.
I checked this again and my statement was mostly not right, sorry. It
depends. The XP scaling affects applications that are not DPI aware, and when
it does apply, it is different. It is trying to avoid scaling making things
less sharp, but Windows Explorer does scale icons at 1.25. Other apps do
different things.
On Win7, Chrome doesn't scale icons, URL bar, or content on Win7 at 1.25, but
it does scale tab title text. On Win10, it scales all of these.
It would be helpful to know the reasoning for this variation in decision.
I've filed bug 1271893 for the 1.5 step.
I'm willing to think about a 1.25 step for the subsequent release. My initial
impressions were not good. Tabs are the worst (bug 995733). There's also the
https/hamburger
content, wrong size icons in menus. The impression is that the app was not
designed for scaling (and it wasn't).
Browsing the web immediately finds similar issues such as the fuzzy youtube
icon, and wonky guardian hamburger, but most of the content on each page is
good. Text of course is sharp, except where bitmap renderings are provided,
and so one can get used to the problems. Some people will prefer this.
I'd be more comfortable using 1.25 when we know the user has explicitly chosen
to set that value, rather than using 1.25 based on EDID.
In GTK versions with this change, I think we can be much more sure of where
a non-96 dpi comes from:
https:/
That is in
https:/