Closed MarcHagen closed 4 years ago
Hey, I'm aware of this issue. It is caused by an update that Waze pushed way sooner than I had expected.
As a temporary workaround, you could install this small userscript that counteracts the changes made by Waze. It will also help with all other userscripts.
Hey, I'm aware of this issue. It is caused by an update that Waze pushed way sooner than I had expected.
As a temporary workaround, you could install this small userscript that counteracts the changes made by Waze. It will also help with all other userscripts.
Perfect, thanks for the temporary workaround.
This issue has been fixed with the recent release :)
And the "formatted" code from vendor.js: