News for hackers. Stuff that matters.

A comment on 300ms tap delay removed on Chrome for Android. Parent comment

Re:300ms tap delay removed on Chrome for Android by bluthru on Friday December 13, 2013 @12:09PM (#6901582)
Especially now that phones have high-res screens. No need for everything to be dumbed down to a single column that's 8 words wide.
[ Parent | on HN ]
Re:300ms tap delay removed on Chrome for Android by jaffathecake on Friday December 13, 2013 @12:26PM (#6901690)
It's not about resolution, it's about angle of view (http://en.wikipedia.org/wiki/Angle_of_view).

My phone has the same resolution as my computer monitor and 45" TV. But due to size and viewing distance, the same font & image sizes shouldn't be used on all.

This is why we have ppx/device-pixel-ratio on the web.

[ Parent | on HN ]
Re:300ms tap delay removed on Chrome for Android by altcognito on Friday December 13, 2013 @06:10PM (#6903417)
No, it's about resolution (or a unit of length, but that boils back down to resolution): http://omnicognate.wordpress.com/2013/01/07/in-css-px-is-not...
[ Parent | on HN ]
Re:300ms tap delay removed on Chrome for Android by jaffathecake on Saturday December 14, 2013 @02:36AM (#6905039)
Your link appears to agree with me. That ppx/device-pixel-ratio is used to make CSS pixels an angular measurement. Although I haven't encountered a TV browser that does this properly yet.
[ Parent | on HN ]
Re:300ms tap delay removed on Chrome for Android by gohrt on Friday December 13, 2013 @01:01PM (#6901895)
> dumbed down

???

Longer columns doesn't take higher intelligence, it just strains your eyes.

http://baymard.com/blog/line-length-readability

Have you ever seen a print edition of the NYT or WSJ?

[ Parent | on HN ]