Hotkeys don't work (... sometimes)

Steps to reproduce

Ever since commit bf05a43, the admin UI depends on grunt-contrib-uglify with a version range specifier of ^3.3.0 for its minification needs, i.e. any version 3.x.y with x >= 3 is fine. The most recent version of this Grunt plugin is, in fact, 3.3.0, and it in turn depends on uglify-js^3.3.0, meaning---again---any version 3.x.y with x >= 3.

Normally, when building Opencast, Maven runs `npm install`, which should fetch the latest versions matching the given version ranges of all the dependencies. However, npm (and probably other systems in the chain between the npm registry and Opencast as well) does caching, and so it might happen that there is a matching but older version of a dependency still lying around somewhere, which is then used instead. Don't ask me to reproduce this; I couldn't, but the effects of this (see below) were seen a few weeks/months back on {legacy,stable,dev} and I saw it on at least one other machine.

The problem with all this is: Version 3.3.2 of UglifyJS (and potentially other versions before, I didn't check) had a bug (see, which in our case affected the registration of the hotkeys. The minification changed the semantics of the original code and thus broke it. This bug is fixed since version 3.3.3, but if you somehow get an older version into your build, keyboard shortcuts might be broken.


Julian Kniephoff
May 28, 2018, 4:59 AM
Sven Stauber
May 3, 2018, 8:20 AM

Oh, this kind of explains why hotkeys always worked for us

Julian Kniephoff
May 3, 2018, 8:11 AM

See for an issue concerning a possible resolution of this problem.

Also see the discussion on the mailing list:!topic/dev/jCqzhkIUCZU

Fixed and reviewed
Your pinned fields
Click on the next to a field label to start pinning.


Julian Kniephoff


Julian Kniephoff


Non Functioning

Tags (folksonomy)