Meph wrote:I think you're just overreacting because you're not used to the change.
Obvious it doesn't effect you otherwise you wouldn't be doing the Mozilla apologist dialogue.
Meph wrote:I think you're just overreacting because you're not used to the change.
streetwolf wrote:I'm not sure but I think the patch was originally thought out to provide better looking output on tablets and the like. It seems like it worked for you but for desktop users it doesn't fair as well.
malliz wrote:Meph wrote:I think you're just overreacting because you're not used to the change.
Obvious it doesn't effect you otherwise you wouldn't be doing the Mozilla apologist dialogue.
Using the OS DPI is like using Fx Full Page Zoom of 125% on every page. If you like text on steroids and blurry graphics then so be it.
Sure... maybe all the browsers do it this way and Mozilla felt it had to do it the same way. Well... they are wrong. They got it right as it was. Maybe on a Surface Pro Fx 22 looks good but not on a desktop PC with a large monitor.
JayhawksRock wrote:SaphirJD wrote:What a pitty, Thanks to Aurora and Nightly i have found back to my enthusiasm about Firefox... and now the Devs do everything to scare people again away.....
Apparantly you have never tested Alpha 1 builds before. I hope you are not relying on 22 as your work browser. Every day there will be something broken and they are not always secure.
Mark342 wrote:streetwolf wrote:This change, IMO, wasn't given much thought. IE10 does not rely on the OS DPI at least for content based on side by side comparisons of Fx22 and IE10. While IE10's UI is big I don't think it is because it is using the OS DPI.
You are wrong.
Here is a side by side comparison of Nightly and IE10 with DPI set to "Smaller" ( 100%, the default ).
http://i.imgur.com/u5kQGFT.png
Here is another side by side comparison with the same settings, but with DPI set to "Medium" (125%)
http://i.imgur.com/LiymOkk.png
Both browsers were using their now default settings in each test.
That means layout.css.devPixelsPerPx set to -1 and no modifications to zooming.
As you can see, Firefox and IE10 now act the same way.
They scale both fonts and graphics according to the DPI setting.
This scaling affects the UI and content the same way.
The previous way was most definitely wrong.
The only issue I see is they do not yet have higher resolution images for high DPI modes so the graphics in the UI get blurry.
They are already aware of this, and it is being rectified.
StinDaWg wrote:I use NoSquint and only want the page content larger, not the UI.
StinDaWg wrote:The thing is if you set Windows DPI to 150 but check "use Windows XP style scaling" then Chrome and IE will respect that setting and won't blow everything up. Firefox ignores it and scales with the blown up graphics anyways. I use NoSquint and only want the page content larger, not the UI.
StinDaWg wrote:The thing is if you set Windows DPI to 150 but check "use Windows XP style scaling" then Chrome and IE will respect that setting and won't blow everything up.
quirK wrote:It's IMPOSSIBLE that a single zoom setting caters for ALL the websites that we (who use zoom regularly) browse. So a 150% blow-up will not only make everything look blurry, one STILL has to customise the precise zoom settings for individual websites based on screen size, screen resolution, optical acuity and myopic technical web design.
Guys, there is no way your going to convince me that what I see on my screen, with the DPI patch, is acceptable. The ability to change DPI in Windows was primarily to address readability on large screen monitors. The normal DPI of 96 is just to small. Think of this... how come Window apps all scale correctly? I don't have any apps that produce over sized text or blurry images. Yes, at one time many apps never took into account anything above 96DPI but that has been corrected for the most part. Some older apps may still have text problems at 120DPI.
Web design has not met the challenge of large screen monitors. It probably isn't an easy thing to do having to keep different size graphics for different DPI's. The irony is that Fx seems to be concentrating it's efforts away from the desktop to mobile devices which have smaller displays.
Someone mentioned here that only IE and now Fx use the OS DPI value to scale. You'd think Google Chrome would have done this if it was such a great thing. Perhaps Google thinks like I do that using the OS DPI just makes things worse.
streetwolf wrote:XP scaling is provided as a means to accommodate programs that are not DPI aware. Ideally all programs should be DPI aware and this option should be left unchecked. However, if you do this you will come across many apps that all of a sudden will have fuzzy text. CCleaner is such a program. Fx appears to have DPI awareness because it doesn't become fuzzy.
streetwolf wrote:Think of this... how come Window apps all scale correctly?
Pixel wrote:streetwolf wrote:Think of this... how come Window apps all scale correctly?
Can you EXPLAIN what the hell you're talking about when you say this?
streetwolf wrote:I don't see oversized text or icons anywhere in Windows except Fx22 and IE10. How come Windows can't scale these two just like it does every other application or Windows component?