Because we are supporting Internet Explorer 11, it limits the amount of modern JavaScript we can use. […] So I’m dealing with new things that are “old hat” for most people, but I didn’t realize that if you have an element and use classList.add() , you can’t add two classes at the same time in Internet Explorer 11. […] I haven’t done anything with ES6 at all, I’m just trying to get going with vanilla JavaScript that’s going to work in IE. I haven’t found it incredibly difficult, but some people on our team do often use ES6 and transpile it for older browsers.
Another issue was likely related to parsing of HTTP headers:
There was a difference between Firefox and Chrome when it came to CORS. […] For some reason the options we received in the response didn’t actually work in Firefox. […] I checked it out on Chrome and it worked just fine. […] Firefox was freaking out about either order or like literally either uppercase or lowercase. […] About a month after that started happening Firefox had resolved the issue.
Yet another was about dblclick events when double tapping a touch screen:
One is the double clicking on a touch screen, like a surface laptop or a cellphone or a tablet. […] Some platforms, when you double tap the screen on the same point, it will fire a dblclick event in JS. Some other platforms will not, on the same hardware with the same code. See also ● Test262 Report , a dashboard for the ECMAScript conformance test suite ● Babel ● core-js ● polyfill.io Performance Performance ranked #3 in feature areas causing issues in the survey. The option was “Performance (APIs, scrolling, smooth animations)” and some of this may thus be related to scrolling . Some performance-related issues came up in interviews, although we did not focus on it. No attempt was made to get a deeper understanding of these issues for this report, but the quotes may be useful.
Made with FlippingBook - professional solution for displaying marketing and sales documents online