- We'll definitely investigate the F1 key issue. We have a broader bug that causes the whole app to stop responding to keyboard shortcuts if the browser window is not focused first.
- Interesting, we'll look into also adding this behavior. It is indeed a common behavior, specially in diagramming software.
Also, on a Chromebook, F1 is actually the back button. If the back button isn't active (there's nowhere to go back) the moqup help works, but if the back button is active, it simply goes back.
- We'll definitely investigate the F1 key issue. We have a broader bug that causes the whole app to stop responding to keyboard shortcuts if the browser window is not focused first.
- Interesting, we'll look into also adding this behavior. It is indeed a common behavior, specially in diagramming software.