4 ms·
why would they not follow what browsers already do and solely rely on: <meta content="width=device-width, initial-scale=1.0" name="viewport"> this is basi
by leeoniya 11y ago
why would they not follow what browsers already do and solely rely on:
<meta content="width=device-width, initial-scale=1.0" name="viewport">
this is basically a solved problem with pretty much all other vendors having already converged.
instead, they're giving fastclick [1] a reason to live on to polyfill a single, non-conforming vendor :(
[1] https://github.com/ftlabs/fastclick https://github.com/ftlabs/fastclick
- deleted 11y ago[deleted]
- nevir 11y agoEach browser tackles it in a different way (see https://github.com/ftlabs/fastclick#when-it-isnt-needed https://github.com/ftlabs/fastclick#when-it-isnt-needed): * Chrome checks the viewport meta, as you mention * IE looks for CSS (touch-action: manipulation) on elements The change being made to WebKit will allow it to honor the viewport meta approach (e.g. when it disables scaling), just like Chrome does. So, if anything, IE is the odd one out now.