This face can take it.

I'm sorry I haven't responded here in a while. As you may know, I quit Waze for a while and then returned with a bang.

Amongst the major disasters introduced by the latest WME update was a relatively minor problem - date/time display in WME is using a stupidly-long format. Glodenox has designed a simple fix here.

I've incorporated this into WME Fix UI with a minor version update to 1.5.1. Please note that this is not, like my other fixes, a fix that is optional. If the script is running, the fix is in - so please let me know if it causes any problems. If it does, I'll make it a selectable option.

A minor update to the minor update: the new date formatting now shows the year (following user feedback from AntonioGMuriana) and also abbreviates the full month.

AntonioGMuriana wrote:Can I disable this functionality? The date does not include the year so I don't know if an edit is one week or three years old!!!

I credited your response in the WME update thread, but missed your response here.

As you can see, I've added the year back in. I don't want to get too involved in tweaking this particular item, as HQ have acknowledged that there are major problems with the last update and it looks like they may step back a little to get scripts working again.

This particular fix was very quick to do indeed, as long as I just added it to always run. If there turn out to be other minor problems with it, it will take me about an hour or two to turn it into a selectable option: the rest of my script works mainly by adding/removing bits of CSS to/from the page. This fix adds some environment variables that are missing from the page, so I'll have to experiment with whether I can remove them again.

But if it's needed, I'll manage it.

Version 1.5.3, now live on Greasyfork, correctly deals with localised WME as detailed above. The new date formatting for the closures dialogue is also added.

Note that there appears to be a problem with the date/time being completely missing in the UR dialogue when UK English is the selected language. This problem is not caused by either my additions to WMEFU, or by Glodenox's script. As far as I can tell it is a native WME bug and I'm seeing the same problem with no scripts running at all.

I have spent about 3 hours trying to work out what is causing this, but without success. No doubt someone smarter than me (Glodenox ) will figure it out and I'll rip off the solution.

Glodenox wrote:Now you're making me blush

Well you make me blush, because you knew where to find this! I'm just hacking at it here.

The fix you suggested wasn't quite right - I had to use So, version 1.5.4, now on Greasyfork, restores the missing date from URs when WME language is set to UK English.

We (the UK Admins) are also looking into why the translation is incorrect in the first place. It looks like it is correctly translated on Transifex. The problem has also previously been referred to HQ, who thought it had been fixed. We'll chase that up.

It's been a while since an update, but version 1.6 is now live on GreasyFork - my late Christmas gift to you all.

My initial reason for updating was the new Map Comments - but when I looked at the dialogue, it seemed reasonably compact so I left it alone. However, I have added compression tweaks for both the Feeds and Drives tabs with the normal objective - getting more information on-screen without scrolling. Note that I've enlarged the Trashcan button for feed items - since I keep missing it and doing so moves the map. I've also added tweaks for the time-based restriction pop-ups, which were starting to seem freakishly large to me.

The last few minor updates were concerned with the accidental changes made to time formats by the WME developers. Although they've now fixed the formats, it seems to me that seeing the time of an edit is a useful thing. There are implications with making that information visible by default in WME (I don't want my boss knowing if I made that edit during working hours ). But having it made visible only by a script likely to be used by serious editors seems like less of a problem. I've therefore decided to leave my time format tweaks in the script.

Having map comments visible seems to me to be very important. I would have been happy if Waze had made some sort of change to automatically re-enable it on a schedule, or on refresh, or panning a certain distance etc. Since it is currently easy to forget that it's disabled, I've added functionality that turns the WME toolbar background bright orange when the layer is disabled. For the sake of simplicity, the layer is only checked when my script loads, the map is zoomed, or the map is panned.

I've added a fix for inconsistent formatting of the character counter for the UR comment box - as mentioned on the forum here - because we all know how long it's likely to take Waze to fix it.

Lastly, I decided I might have been too nice to you - so I added an annoying pop-up box to announce an update to the script and give brief details.

I can reproduce this issue - but not as consistently as posts above suggest.

• In the production WME with Chrome I may have seen it once or twice, but cannot reproduce the vast majority of the time
• In prod WME with Firefox (where I only run WMEFU) I cannot reproduce at all
• I don't have Safari to test and (if it makes a difference) I'm on Windows 7
• In beta WME, I can reproduce 100%: moving to a new item doesn't open it until the second click.

The last behaviour allowed me to identify the likely problem. It's actually a "bug" with the new feature that turns the toolbar orange when Map Comments are off.

Because I couldn't find an easy way to detect the layer state being changed, I check the state of the Map Comments layer on 2 WME events: moveend (fires after the screen has been panned) and zoomend (fires after the map zoom has been changed). At this point, my script crashes on beta WME and prevents the opening of the UR/MP. And the reason? The Map Comments layer has a different ID between prod & beta!

Why this should be, I don't know. Obviously I didn't test sufficiently in beta though. I should be able to fix this by testing for both layer names and gracefully handling the absence of either. More annoying is the fact there is no element identifier I can reliably use to "find" the MC layer (when hiding the ave speed cam box, I search for the ID "fwdSpeedCameraCheckbox" which is independent of language). So this means that, every time Waze change the layer ID, I'll have to fix the script.

Update will be out after breakfast.

Glodenox wrote:I might be missing something

Of course you are not. In case you haven't realised, you know a lot more about the internal workings of WME than I do.

I'm currently checking the state of the checkbox in the layers menu - and that's because it was the first way I found to check whether the layer was on or not. Obviously checking the actual layer visibility would have been better - if I'd known where to look.

I'll do some double-checking to make sure that layer name doesn't get localised (Waze do tend to keep internal names in English) and update the script to use that test instead.

New version (1.6.1) updated with a fix for the Map Comments toolbar highlight bug, which was interfering with clicking on Feed items.

If you continue to have problem selecting Feed items, please let me know. In particular, let me know

• What browser
• Whether the problem is in the beta or production WME
• What language you have WME set to
• If there are any errors in the console

I've also made a change to the "Updated" pop-up. When the language settings don't match the WME location, WME reloads to change language and the pop-up was appearing again.