Tell me about it. I have tried my darndest to use types and tests to make things predictable. But there is always something that comes up.

It might be Javascript itself. It could also be the endless permutations of environments(browsers, resolutions, devices, etc) that we have to cater to.

Front End Web Development is hard.

It would be much easier without the moving target of new Javascript features that browsers have to keep up with. With a real, mature, nonbroken language there would be no need to add new features every year. Someone said that Python is badly suited for the web because not event-oriented, whatever that means. Well, JS didn't have async/await until recently, and there's still lots of code that uses promises, yet even promises aren't supported by ancient browsers. It would have been so much easier to use a language that had ironed its sophomore mistakes somewhere on the desktop, before the web limelight. Instead, they created an all-new "web language" to ensure decades of volatility and reinventing the wheel for all the world wide web...

A friend of mine worked on JavaScript at Netscape. He says he's sorry.

Thanks, I appreciate it as I go on to the third day of trying to find why Javascript cannot get the correct width of an image but only under some circumstances unconnected to the JS code.

Maybe sometimes it is not loaded yet? (Just a wild guess)

Yes, that's the typical explanation, but no, the images are most definitely loaded, thanks.

Meaning you have received the event that it has been loaded?