In non-mash, when the first-run tutorial is running, most keyboard accelerators do not work. For example, Ctrl-N will not open a new window, Alt-Shift-S will not open system tray, etc. However, accelerators like screen brightness and volume still work.

With mash, most keyboard accelerators start working (or try to work). Ctrl-N will open a new browser window, though it is hidden. Alt-Shift-S will open the system tray.

I don't know how non-mash is suppressing the accelerators. There's no code in //ash accelerator handling that checks first-run state. Likewise the first-run app JavaScript isn't doing anything special with keyboard events. Somehow it's a side effect of the first-run widget being fullscreen, containing a web view, being focused, or some combination.

Mash must be treating accelerators differently (ash registering them up-front) that bypasses this code path.

alemate/afakhry, do you know off the top of your head how the first-run tutorial suppresses keyboard accelerators?