- Having to test in every single browser. Not being able to rely on iOS behaving the same way as its counterparts. - iOS usually causes the most issues at this point. Safari and Chrome on iOS can be modern in some ways, but outdated in others - Varying JavaScript implementations that differ from browser to browser. - The javascript part, I know if I use webpack and babel it could save my problem. But native support is always what i looking for. - Running code through transpilers often means that code is bloated and large file sizes - Knowing when we can start to use newer browser APIs. - Not knowing the little nuances of things that are different, or which newer web specs aren't yet fully supported on some browser or another. - Discovering the lowest common denominator. caniuse.com is the best resource thus far. - Multimedia - using audio/video tags isn't always consistent among browsers. Specifically I run into issues when src attribute was set dynamically (it was Safari I believe). - Audio files - there should be one format for every browser - lack of consensus vendor support for some APIs, e.g. web speech api
JavaScript
JavaScript
78
Other
Knowing
25
Other
Media
23
Other
Mobile
34
- Mobile testing, because:
- Responsive mode on desktops doesn't always emulate mobile perfectly - Debugging on mobile, even through possible, is not plug'n'play
Made with FlippingBook - professional solution for displaying marketing and sales documents online