Re: [css-values] The length unit 'Q' (quarter of millimeter)

On 2013-11-18 10:37 (GMT-0800) Sylvain Galineau composed:

> "Simon Sapin" <simon.sapin@exyr.org> wrote:

>> Rik Cabanier wrote:

>>> I'm a little worried that text that is set in 'q' will look blurry on
>>> screen (since it doesn't fall on a CSS pixel), but maybe browsers
>>> already fix that. If not, text in converted 'q' units today already
>>> looks blurry.

>>The q unit wouldn’t change anything in this regard.

>>It’s already easy to to specify non-integer-px font sizes accidentally
>>with percentages and em units. Browsers typically use hinting to keep
>>text crisp (even at integer-px sizes)

> I agree. This should not be worse than the pt unit, which remains popular
> and is a fractional number of CSS pixels.

The pt unit no longer exists except in old browsers, Konqueror when 
configured to use the KHTML engine, or any other browser that may exist that 
uses the KHTML engine. Pt for quite some time has been a synonym for px in 
Blink, Gecko, Trident and WebKit.

There is a workaround that can work in Gecko browsers, which provide the 
mozmm unit for those who need or want absolute units that render physical 
dimensions accurately on accurately configured displays.

It is unfortunate that web pages dependent on absolute units must now append 
instructions that intended use of a page requires use of an old, Gecko or 
KHTML browser, or even a particular operating system to run it, to be able to 
do what it was originally designed to do, and worked well enough before the 
retirement of absolute units.

e.g.:
http://www.infobyip.com/detectmonitordpi.php (broken)
http://browserspy.dk/resolution.php (broken)
http://fm.no-ip.com/Auth/dpi-screen-window.html (modified to use mozmm)
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Received on Monday, 18 November 2013 20:23:53 UTC