God forbid they tested across the multiple common browsers out there other than Chrome. Every other software development company creating a web app does that, why doesn't one of the biggest?
Sadly no, ever web app company definitely doesn't test under Firefox. I'm at the point where I use Firefox for general web browsing and Chromium for most web apps.
In the last 5 years I've run across maybe 1 site that didn't work properly in Firefox. And another that MIGHT not have worked right, but I was only guessing it was related to FF.
However, since FF dropped PWA support I do use Chrome for a handful of sites that either are PWAs or you can use Chrome's open as application feature, which is real nice for a few things. Is that what you mean by "Web Apps"?
The script attempted to modify a div's background color using document.body.removeChild, but as the script was loaded in the HTML head, the DOM had not loaded
Isn't that how it works/always worked? When i was learning html/js ages ago i had to use some event listener (DOMContentLoaded i think) or put the script just before </body> (for any code that should run on load and interacts with the DOM).
And how do you change the background by removing a child?
And how do you change the background by removing a child?
The removed child could also have a background color, and it could span the entire area of the parent element.
But it's weird because the quote says "modify a div's background color", and this way you don't actually modify that, but only it's appearance.
Or maybe it's done with some CSS trickery, looking for a specific child in it's selector?