Keyboard shortcuts for Spread turn arrows and Hide turn arrows only works on settings tab

Map Editors Community WME Production Bugs
1

Is this a…:
Standard bug
Steps to reproduce this issue:
The keyboard shortcuts for Hiding (A) and Spreading (S) turn arrows are not working unless the left panel is on the settings tab.

To reproduce:

  1. Select a segment
  2. Have the left panel be in any tab except the settings tab.
  3. Tap A or S to hide or spread turn arrows.
  4. Nothing happens.
  5. With the segment still selected, select the settings tab.
  6. Tap A or S to hide or spread turn arrows.
  7. Tada! The shortcuts work again.

This was tested in incognito with no scripts or extensions.

Environment where the bug occurs…:
All environments
Permalink:
Anywhere on the map
Browser name and version:
Chrome 141.0.7390.123 (Official Build) (arm64)
Are you using scripts? Please detail which ones.:
No

d8b9dc75-35ed-4643-83e4-5faf8f99be06.png
d8b9dc75-35ed-4643-83e4-5faf8f99be06.png378×108 6.38 KB

5 Likes
New WME v2.323
Turn arrow display hotkeys only work when settings tab is open
Nova Versão WME v2.331
Turn arrow display hotkeys only work when settings tab is open
2

Hello @ojlaw,

Thank you for your report!
I have filed an internal ticket to address this issue. I’ll keep you posted on further updates.

Kind regards,
Olesya

4 Likes
4

I noticed this too, thanks for raising the bug.

5

Is this a…:
Standard bug
Steps to reproduce this issue:

  • Select a segment to display turn arrows
  • Open “Settings” tab
  • Press A or S and observe turn arrow display options changing (expected behavior)
  • Switch to a different tab in the left sidebar, or close the tab altogether
  • Press A or S and observe turn arrow display options NOT changing (unexpected behavior)

Environment where the bug occurs…:
All environments
Permalink:
Applicable to any location
Browser name and version:
Chrome 144.0.7500.5
Are you using scripts? Please detail which ones.:
No scripts (incognito)

3 Likes
6

Hey @Olesya-Staff,

are there any news when this is getting fixed / updates on the internal ticket? The bug still persists, it’s been almost 2 months now. :wink:

1 Like
7

Hi @Variatox,

The issue has been worked on and the fix for it is currently in the release pipeline.

Thank you for your patience!

3 Likes
8

Hello all,

I’m happy to let you know that the fix has landed in WME production; therefore, I’ll be marking this issue as fixed.

Thank you so much for your patience!

Best,
Olesya

2 Likes