Besides not considering these two hotkeys, breaking those is also a consequence of the design flaw from rP17594 desribed here.

Several ways to address this have been discussed with Vladislav at the time of the review of this diff and after the concern was raised:

• Doing it as before and only toggling at the begin and end of a cinematic path. (Still overwrites the user config).
• Saving the hotkey toggle states in the config or some other C++ variable. (Still bad hardcoding of an XML GUI object and of a hotkey in a C++ graphics component)

But since developers and modders should be able to deal with the cinematics in arbitrary ways and
because the C++ code should be as agnostic of hotkeys as possible (for the same reason),
the JS code itself should decide when and where it hides something based on the fact whether a path is playing or not. Patch incoming.