even if the segment is “simplifiable”… will be fine with the aerial
I’m running Chrome 59.0.3071.115, and just tried - it’s working for me at this time… Strange. Try again, maybe?
Same here, I had to repair again and it worked fine after (Chrome 59)
Hi. Today i cant repair the toolbox in chorme for windows. Then i delete and when try reinstall, error “Image decode failed” :(.
[attachment=0]error toolbox.png[/attachment
Same Chrome version, tried again after a full reboot and still nothing, it simply does nothing after I click on “Repair” 
I know it takes me 2 or 3 Repair attempts sometimes to get it to stick.
Tried it too, it made no difference. I can see the color changing during the click, so it’s being read, but does nothing.
Toolbox 1.7.9 is released for Chrome:
1.7.9 (20170712)
Fix: Chrome extension should no longer report as corrupt
Fix: Auto-complete of the city name in properties editor was broken (#399)
New: Configuration option whether to show parking type popups (#397)
New: Attributes to segment list columns: tunnel, unpaved, headlights required (#398)
Update: Updated country rights settings for Ukraine
The Firefox addon is submitted for code review (this has to be done for each release now) and will therefore be available somewhat later. It should auto-update when reviewed.
1 Like
“Repair Corruption” no longer needed after restart of Chrome. A million THANKS!!!
Thanks @Bellhouse!!
Thanks! Working for me as well.
Awesome, thanks a bunch
I confirm that after closing Chrome navigator and loading again the WME the TB loads sucessfully and in the Extensions section the “Repair Corruption” has gone.
I have to know - was the corrupt/repair problem due to the filesize of bootstrap.js? :?:
Working like a charm again, thanks!
Thank you so much for fixing this extremely valuable script!!!
Sent from my iPhone using Tapatalk
The update is greatly appreciated, in case you couldn’t tell from the previous responses 
Awesome…thanks!!!
I’m glad to hear that the Chrome extension is now working again for all of you!
Yes, Sir, we owe this one to your excellent detective work of digging out the issue with the file sizes. We added a comment line to the bootstrap.js file, and that alone seems to have done the job.
Huge thank you for the recent update fixing the chrome error!!!