3 ms·

> Now I would turn it up to 150% "text size" but that breaks SO many native Windows applications (e.g. pushing text off the viewable area) and does the same on

by exDM69 14y ago

> Now I would turn it up to 150% "text size" but that breaks SO many native Windows applications (e.g. pushing text off the viewable area) and does the same on Linux too (Ubuntu). In the web too. For too many years it was standard to use hard coded font sizes and specifying measurements in pixels in CSS. It's about time web designers start thinking about accessibility and start using flexible font sizes and using em's (unit of length relative to text size) in web designs. Even when it means doing small compromises in the design and you can't make the web site pixel perfect with regards to the photoshopped design mockups.

zokier 14y ago
Pixels in web (css) are resolution independent. They are basically defined to be equivalent to a pixel on a desktop 96 PPI display. So using pixels in CSS is fine, if bit confusing. And of course browsers do all sorts of silly things, I can't recall if eg gecko has enabled PPI scaling on default. edit: reference: http://www.w3.org/TR/css3-values/#absolute-lengths http://www.w3.org/TR/css3-values/#absolute-lengths
drivebyacct2 14y ago
Huh? That's not entirely accurate and besides, Gecko and Webkit have been doing full page scaling for years and I presume IE is as well.
snowwrestler 14y ago
Pixels dimensions and font sizes in CSS are fine because the browser apply a multiplication factor to the CSS values, so that the page and fonts display correctly on a high res screen. This is how Mobile Safari works. The problem with websites is the image files--JPG, GIF, and PNG. The resolution is locked in when the graphic is made, so files made for the the low-res web will look blurry and pixelated when the browser scales them up for a hi-res display.
- w1ntermute 14y ago
  > The problem with websites is the image files--JPG, GIF, and PNG. The resolution is locked in when the graphic is made, so files made for the the low-res web will look blurry and pixelated when the browser scales them up for a hi-res display. Such sites aren't blurry in absolute terms, just in relation to sites that have been optimized. That is, they look the same as they would on a standard screen.

by exDM69 14y ago

zokier 14y ago

Pixels in web (css) are resolution independent. They are basically defined to be equivalent to a pixel on a desktop 96 PPI display. So using pixels in CSS is fine, if bit confusing. And of course browsers do all sorts of silly things, I can't recall if eg gecko has enabled PPI scaling on default. edit: reference: http://www.w3.org/TR/css3-values/#absolute-lengths http://www.w3.org/TR/css3-values/#absolute-lengths

drivebyacct2 14y ago

Huh? That's not entirely accurate and besides, Gecko and Webkit have been doing full page scaling for years and I presume IE is as well.

snowwrestler 14y ago

Pixels dimensions and font sizes in CSS are fine because the browser apply a multiplication factor to the CSS values, so that the page and fonts display correctly on a high res screen. This is how Mobile Safari works. The problem with websites is the image files--JPG, GIF, and PNG. The resolution is locked in when the graphic is made, so files made for the the low-res web will look blurry and pixelated when the browser scales them up for a hi-res display.

w1ntermute 14y ago
> The problem with websites is the image files--JPG, GIF, and PNG. The resolution is locked in when the graphic is made, so files made for the the low-res web will look blurry and pixelated when the browser scales them up for a hi-res display. Such sites aren't blurry in absolute terms, just in relation to sites that have been optimized. That is, they look the same as they would on a standard screen.