# \[Script\] WME UR FAST
**URL:** https://www.waze.com/discuss/t/script-wme-ur-fast/347096
**Category:** Addons, Extensions, And Scripts
**Created:** [February 10, 2024, 7:17pm UTC](https://www.waze.com/discuss/t/script-wme-ur-fast/347096 "2024-02-10T19:17:11Z")
**Posts on this page:** 19
**Page:** 2
### Author:  [@bruno\_bgo](https://www.waze.com/discuss/u/bruno_bgo)
#### Post date: [December 9, 2025, 3:33pm UTC](https://www.waze.com/discuss/t/script-wme-ur-fast/347096/21 "2025-12-09T15:33:18Z")
Sorry, I hadn’t seen that option.
Thanks 😅
---
### Author:  [@EsdrasFarao](https://www.waze.com/discuss/u/EsdrasFarao)
#### Post date: [December 11, 2025, 1:36pm UTC](https://www.waze.com/discuss/t/script-wme-ur-fast/347096/22 "2025-12-11T13:36:12Z")
I don’t know if it’s a bug, but when I hold down CTRL and click on a message shortcut, it works correctly, but when I click “send,” the UR closes automatically. This didn’t happen in the last version.
---
### Author:  [@sulstore](https://www.waze.com/discuss/u/sulstore)
#### Post date: [December 11, 2025, 2:08pm UTC](https://www.waze.com/discuss/t/script-wme-ur-fast/347096/23 "2025-12-11T14:08:33Z")
@EsdrasFarao On second thought, that’s the behavior. If you used closing text for the UR and sent it, why should the UR remain open?
---
### Author:  [@EsdrasFarao](https://www.waze.com/discuss/u/EsdrasFarao)
#### Post date: [December 11, 2025, 2:32pm UTC](https://www.waze.com/discuss/t/script-wme-ur-fast/347096/24 "2025-12-11T14:32:38Z")
You’re right. When we’re used to something and it suddenly changes, we find it strange. But I hadn’t thought about it that way.
I discovered this by accident, because I clicked on “close” when I actually wanted to click somewhere else, and then I realized that sending the message closes the UR (User Interface), which didn’t happen before.
But really, this isn’t a problem…
---
### Author:  [@EsdrasFarao](https://www.waze.com/discuss/u/EsdrasFarao)
#### Post date: [December 11, 2025, 3:09pm UTC](https://www.waze.com/discuss/t/script-wme-ur-fast/347096/25 "2025-12-11T15:09:18Z")
We definitely have a bug now…
---
### Author:  [@turbomkt](https://www.waze.com/discuss/u/turbomkt)
#### Post date: [December 11, 2025, 3:20pm UTC](https://www.waze.com/discuss/t/script-wme-ur-fast/347096/26 "2025-12-11T15:20:35Z")
> [@sulstore](#):
>
> On second thought, that’s the behavior. If you used closing text for the UR and sent it, why should the UR remain open?
What if you’re using the issue tracker to navigate reports and want to move on to the next one in the list?
---
### Author:  [@sulstore](https://www.waze.com/discuss/u/sulstore)
#### Post date: [December 11, 2025, 5:18pm UTC](https://www.waze.com/discuss/t/script-wme-ur-fast/347096/27 "2025-12-11T17:18:48Z")
> [@turbomkt](#):
>
> > [@sulstore](#):
> >
> > On second thought, that’s the behavior. If you used closing text for the UR and sent it, why should the UR remain open?
>
> What if you’re using the issue tracker to navigate reports and want to move on to the next one in the list?
> [@\[Script\] WME UR FAST](https://www.waze.com/discuss/t/script-wme-ur-fast/347096/20):
>
> Just uncheck that option.
---
### Author:  [@turbomkt](https://www.waze.com/discuss/u/turbomkt)
#### Post date: [December 11, 2025, 8:32pm UTC](https://www.waze.com/discuss/t/script-wme-ur-fast/347096/28 "2025-12-11T20:32:32Z")
I was just answering your question as to why the editor would want the UR to remain open.
Maybe @EsdrasFarao can verify that setting.
---
### Author:  [@sulstore](https://www.waze.com/discuss/u/sulstore)
#### Post date: [December 11, 2025, 8:55pm UTC](https://www.waze.com/discuss/t/script-wme-ur-fast/347096/29 "2025-12-11T20:55:11Z")
> [@turbomkt](#):
>
> I was just answering your question as to why the editor would want the UR to remain open.
>
> Maybe @EsdrasFarao can verify that setting.
I think there was a misunderstanding.
When he mentioned keeping it open, he was referring to marking it as “Resolved” or “Unidentified.” This is actually a bug, because the action (last state) is defined in the button, and when the button isn’t used, the last action is executed. I’ll fix this today; it’s quite simple.
Regarding my response to you, when the user uses the issue tracker, the option there refers to closing the UR window after it’s marked as unidentified or resolved. So they are distinct things.
---
### Author:  [@bruno\_bgo](https://www.waze.com/discuss/u/bruno_bgo)
#### Post date: [December 12, 2025, 1:55pm UTC](https://www.waze.com/discuss/t/script-wme-ur-fast/347096/30 "2025-12-12T13:55:46Z")
Today the same thing happened, I wrote the message, but when I clicked send, the UR closed.
---
### Author:  [@sulstore](https://www.waze.com/discuss/u/sulstore)
#### Post date: [December 12, 2025, 3:50pm UTC](https://www.waze.com/discuss/t/script-wme-ur-fast/347096/31 "2025-12-12T15:50:27Z")
> [@bruno\_bgo](#):
>
> Today the same thing happened, I wrote the message, but when I clicked send, the UR closed.
Correction made in version 1.6.1 (Submitted to Google, awaiting approval)
---
### Author:  [@WazingArch](https://www.waze.com/discuss/u/WazingArch)
#### Post date: [October 23, 2026, 6:02am UTC](https://www.waze.com/discuss/t/script-wme-ur-fast/347096/32 "2026-10-23T06:02:44Z")
Can you please fix feature “Bring window into the visible area”. Currently this feature has stopped working, and my UR window is stuck outside visible area.
---
### Author:  [@sulstore](https://www.waze.com/discuss/u/sulstore)
#### Post date: [October 23, 2026, 11:52am UTC](https://www.waze.com/discuss/t/script-wme-ur-fast/347096/33 "2026-10-23T11:52:01Z")
Hello, which version are you on?
---
### Author:  [@WazingArch](https://www.waze.com/discuss/u/WazingArch)
#### Post date: [October 23, 2026, 11:58am UTC](https://www.waze.com/discuss/t/script-wme-ur-fast/347096/34 "2026-10-23T11:58:08Z")
I am using **v1.8.1**
---
### Author:  [@sulstore](https://www.waze.com/discuss/u/sulstore)
#### Post date: [October 23, 2026, 12:22pm UTC](https://www.waze.com/discuss/t/script-wme-ur-fast/347096/35 "2026-10-23T12:22:37Z")
Could you take a screenshot of how the window appears for you? In this version, Waze itself handles the positioning, so this button is no longer needed; I will remove it in the next update.
---
### Author:  [@WazingArch](https://www.waze.com/discuss/u/WazingArch)
#### Post date: [October 23, 2026, 12:46pm UTC](https://www.waze.com/discuss/t/script-wme-ur-fast/347096/36 "2026-10-23T12:46:29Z")
> [@sulstore](#):
>
> Could you take a screenshot of how the window appears for you? In this version, Waze itself handles the positioning, so this button is no longer needed; I will remove it in the next update.
---
### Author:  [@sulstore](https://www.waze.com/discuss/u/sulstore)
#### Post date: [October 23, 2026, 1:28pm UTC](https://www.waze.com/discuss/t/script-wme-ur-fast/347096/37 "2026-10-23T13:28:10Z")
Access Chrome DevTools (right-click \> Inspect).
Then, go to Application \> Local Storage \> [waze.com](http://waze.com) and look for:
WMEURFASTrootPosition
WMEURFASTrootScale
WMEURFASTcontainerSize
Select them one by one; to the right of the filter field, you will see an “X”—click it to delete the key.
---
### Author:  [@WazingArch](https://www.waze.com/discuss/u/WazingArch)
#### Post date: [October 23, 2026, 2:11pm UTC](https://www.waze.com/discuss/t/script-wme-ur-fast/347096/38 "2026-10-23T14:11:17Z")
This doesn’t work
> [@sulstore](#):
>
> 
>
> Access Chrome DevTools (right-click \> Inspect).
>
> Then, go to Application \> Local Storage \> [waze.com](http://waze.com) and look for:
>
> WMEURFASTrootPosition
> WMEURFASTrootScale
> WMEURFASTcontainerSize
>
> Select them one by one; to the right of the filter field, you will see an “X”—click it to delete the key.
---
### Author:  [@sulstore](https://www.waze.com/discuss/u/sulstore)
#### Post date: [October 23, 2026, 3:03pm UTC](https://www.waze.com/discuss/t/script-wme-ur-fast/347096/39 "2026-10-23T15:03:26Z")
That’s strange; try disabling the script to check.
[Previous page](https://www.waze.com/discuss/t/script-wme-ur-fast/347096.md?page=1)