4 ms·
that's a load of bollocks. if google wants a better web, he needs to work toward better standards. implementing a vendor specific api by fiat with broken detect
by LoSboccacc 9y ago
that's a load of bollocks. if google wants a better web, he needs to work toward better standards. implementing a vendor specific api by fiat with broken detection is what fucked the web in the first place!
same with apple - "now we'll ignore user-scalable=no and screw every responsive webapp out there"
instead of user punishing badly behaved application, vendor are indiscriminately breaking well behaved apps whether they're doing the right thing or not (ie. apps that use em and thus respect user accessibility settings)
this leaves both developers AND users with a sub-par browser experience - like all canvas games out there now get zoomed on double taps, an animation which is often enough to stress the device gpu so much that the browser crashes.
I'm all for improving the web, but there are ways that work and there's this force feeding crap to developer without tough and foresight, and we as a community need to call what's good and what's crap for what it is.
- Spivak 9y agoFine, I'll call out that it's good. I mean honestly you should have seen the writing on the wall with user-scalable: it inhibited the user from doing something they wanted to do, it hurt accessibility, it made websites imperceptibly inconsistent, and there isn't a good way of asking the user if they would like to disable zoom.
- jhasse 9y ago> and there isn't a good way of asking the user if they would like to disable zoom. Whats wrong with "This page wants disable zooming. Allow?"? That would fix the canvas web game usecase.
- LoSboccacc 9y agoShut the W3C down, call Mozilla, close the Acid pages, now Spivak calls out what's good for the web. You know what's good for the web? Standards. Standards that are thoughtful and consistent.
- Spivak 9y agoSince you want to be pedantic the user-scalable and user-zoom viewport tags aren't an official standard. They currently exist in the CSS Device Adaptation Module Level 1 Working Draft. Here are the comments on the property: > Authors should not suppress (with user-zoom: fixed) or limit (with max-zoom) the ability of users to resize a document, as this causes accessibility and usability issues. > There may be specific use cases where preventing users from zooming may be appropriate, such as map applications – where custom zoom functionality is handled via scripting. However, in general this practice should be avoided. > Most user agents now allow users to always zoom, regardless of any restrictions specified by web content – either by default, or as a setting/option (which may however not be immediately apparent to users).
- dx034 9y ago> same with apple - "now we'll ignore user-scalable=no and screw every responsive webapp out there" Maybe because 90% of responsive webapps would be better implemented as standard html websites which would improve performance and help preserving battery.
- somebehemoth 9y ago90% according to whom?
- dx034 9y agoAccording to me. Maybe even higher than 90%. There are a few applications where you need a single-page app. Google Docs is an example or websites that integrate a messenger (e.g. Facebook). For the rest, SPA are a waste of resources and work worse with slow internet. Reddit is a prime example. UX has deteriorated since they switched to loading everything dynamically (again, only me as a source) with no good reason to implement it that way.
- LoSboccacc 9y agowhat the hell are you on about now? responsive web doesn't mean hulking javascript monsters automatically.
- jhasse 9y agoresponsive web also doesnt mean youd need to disable zooming