3 ms·
I find more and more sites using JS for layout and it being an incredibly frustrating experience on my phone. The whole site loads and I'm reading the article f
by donatj 12y ago
I find more and more sites using JS for layout and it being an incredibly frustrating experience on my phone. The whole site loads and I'm reading the article for 4 or 5 seconds and then the js kicks in, scrolling locks, everything stops while The page redraws. On some sites, including Android Centeral of all things, this can stop me from reading text I ALREADY HAVE for upwards of 20 seconds while it reflows. Simply unacceptable.
ALWAYS keep in mind that people are coming to your site for the text almost exclusively. If your stupid JavaScript interferes with the consumption of said text you have failed as a developer.
- protomyth 12y agoAt this point my mobile experience is go to website, read a couple of sentences, watch javascript muck with the layout as you describe, then a full screen popup wanting me to register or download the app, followed by a part of the top of the screen with a app store link for the app, then I get to read the article - maybe. I think we need something that is to websites as markdown is to word processor files.
- donatj 12y agoI'd like a browser that just removes all the CSS and JS and gives me simply the text, like Safaris reader mode, but without the need to ever leave it.
- Mithaldu 12y agoOn the desktop you can get that with Opera 12. It has a toggle to switch off CSS (and of course js) and you can make it a button next to the adress bar.
- chrisweekly 12y agoIt's not exactly what you described, but in my experience "Clearly" (https://evernote.com/clearly/ https://evernote.com/clearly/) does a v nice job delivering a clean, readable, stripped-down "just the text, please" version of a given page.
- TheLoneWolfling 12y agoI find myself hitting the view source button to read (mangled) text in JS source way too often. Or worse, unmangled text in JS source. Or text that's set to display:none until the JS gets to it. If you're going to compile things clientside (looking at you, markdown), at least put the raw text in something the browser can display before the JS compiles it.
- forgottenpass 12y agoI think we need something that is to websites as markdown is to word processor files. We sorta had that, but CSS and Javascript got bolted on.
- Angostura 12y agoI almost reflexively hit the 'Reader View' button on iOS these days, to circumvent that.
- QuercusMax 12y agoThat's what I do as well; unfortunately all the JS jibblin' often makes Safari crash and go into an endless page-reload loop.
- tomjen3 12y agoWouldn't have been much of a problem if CSS hadn't sucked so badly. If you want certain layouts and have to support old browsers you have to use JS.
- briandear 12y agoThe corollary of that is that "have to support old browsers" nonsense. Perhaps if everyone stopped supporting older browsers, the world would be a better place.
- untog 12y agoExcept for people that have to use old browsers.
- donatj 12y agoAs I see it not supporting older browsers is just a middle finger to the poor.
- vacri 12y agoModern browsers are free, and if someone has a particularly old, underpowered computer, there are lightweight ones available (eg Midori - used to use it on an raspberry pi), though admittedly those have less mindshare.
- donatj 12y agoTry hitting a particularly JS intensive site though in Midori on a Raspi. You'll cry. There's no reason for it, it's just wasteful.
- tomjen3 12y agoHow would you implement that in the real world? Because you can't implement it then that argument might as well involve magic.