Can you explain in more detail which problem you're seeing? Is the tab not loading at all?
As for the console errors: that's something that is part of the WME itself and has nothing to do with my script. It is hopefully going to be handled by Waze rather soon™.

Yeah, that seems like the same bug I saw before. I'll try to get it fixed tonight.

Version 0.8.4 has been released, this should fix the issue that downscaling an image can pretty much make it disappear.

I haven't forgotten about that, but this was just a quick fix. Apart from the upscaling and downscaling I haven't changed anything in the latest release. I manage various other userscripts, not all of them publicly, as well as several tools and websites, so I'm spread quite thin along all these projects. That task is somewhat part of the todo-list I have for this script.

I've found some extra time this evening, which I used to improve the script greatly. I first wasted another hour trying to add handles to the image, but failed to progress there. Then I decided to just fix the issue with the resizes being too big (turned out I had my calculations wrong), added a slider that allows you to set the sensitivity of all controls (save for the 45° rotate buttons, those are absolute) and added buttons to stretch and contract the images.

I'm currently still thinking of an alternative way of adding images, but I'd need to work out the maths for it and it doesn't seem easy to me.

I've created a GitHub issue for that request and already added that behaviour to the version in development yesterday. I'm first going to include some other fixes/changes as well though.

I didn't put any limit on the amount of images you can rename. Could it be you're getting some sort of error when you click on the edit button? (you can check for errors in the developer console with Ctrl+Shift+I)

Huh. It seems like TamperMonkey is executing the script sooner than expected (before page load) on your computer. I'll tackle that issue in the next version. For now, you can try to go into the settings of TamperMonkey, open the script, go to its settings and set the "Run At:" setting to "document-end". If I'm not mistaken, that should make TamperMonkey wait long enough for the OpenLayers class to be loaded.

Oh, I hadn't noticed you mentioned GreaseMonkey. They recently changed quite a few things making it a lot more difficult to create userscripts for it. While I won't try to sabotage GreaseMonkey, I'm only going to be testing stuff on TamperMonkey from now on. Their version on Firefox works very well, so I'd advice everybody to use that.

Version 1.0.1 of the script has just been released. This is a technical release that replaces the internal Waze object with W, as the Waze object will be removed in about two months.