services. - It's hard to test in all required browsers in a comfortable way (with possibility to interact with the website, debug problems etc.), especially mobile browsers. - Reliable cross-browser test infrastructure. We no longer test on Firefox due to the cost of keeping it alive. Mozilla would do well to offer cloud infra for Firefox testing. - Conditional Transpiling. Maintaining different bundles for different browser types. Graceful degradation of CSS at scale - The Complexity of the Toolchains that are supposed to help coping with browser compatibility. - Managing the various tools (webpack, babel, etc.) that manage the various polyfills and prefixes required for good compatibility - Inconveniences in the viewport: is the URL bar part of 100vh? - Mobile browser compatibility regardless to when I'm trying to set the web page height to 100% (or flex stretch, or via JavaScript window.innerHeight). This is because of browsers top/bottom native UI bars inconsistency (which appear/disappear on scrolling). - The treatment of viewport units, especially on mobile devices. For desktop: 100vw includes vertical scrollbar width, therefore nigh unusable esp. for windows because it causes hor. scrollbar (often not recognized by developers on macs) For mobile: treatment of 100vh and browser GUI is a PITA. - Lack of cross-browser support for custom built-in elements. - Inability to polyfill something like web component on IE10
Other
Tools
21
Other
Viewport
6
Other
Web Components
10
Made with FlippingBook - professional solution for displaying marketing and sales documents online