Re:300ms tap delay removed on Chrome for Android
by MichaelGG on Friday December 13, 2013 @02:34PM
(#6902411)
Is that what Android Chrome is doing on Hacker News? I remember reading it sometimes and seeing some comments being larger than others. I thought it was some crazy mobile optimization based on votes but it didn't seem to have any logic it to it.
Re:300ms tap delay removed on Chrome for Android
by frik on Saturday December 14, 2013 @03:13AM
(#6905103)
Yes, I that's Android Chrome with its crazy font size guessing :/
Chrome has also more HTML5 related bugs than all other modern browser combined, as JQuery devs mentioned in their blog (2.0 release). It correlates with my own web dev expierence as well. It would be great if Google would employ some QA managers.
Re:300ms tap delay removed on Chrome for Android
by kinlan on Friday December 13, 2013 @01:50PM
(#6902160)
Out of interest what does dolphin do? Does it just leave the text as is?
Re:300ms tap delay removed on Chrome for Android
by buro9 on Friday December 13, 2013 @03:52PM
(#6902839)
Dolphin just lets the web page describe the font size... thus it's all correct.
Chrome and Firefox both try and guess what the font size should be and ignore the web page telling it. Thus the font varies all over the place, though the pattern seems to be depth of text in DOM.
Re:300ms tap delay removed on Chrome for Android
by rits on Friday December 13, 2013 @05:16PM
(#6903221)
Just set the font size to a minimum in Firefox preference and it will stop doing this font resizing. To make text bigger change browser.viewport.desktopWidth in about:config to some smaller value.
You hit some sites, and fonts that should be the same size (and are on the desktop site) are just wildly different sizes.
I'm using Dolphin almost exclusively for this single reason.