Review main Merged

68959[BUGFIX] Prevent currentSubScript re-assignment for secondary modules

Benjamin Franzke CR +2 V +2 Easy +4 −2 updated 05/01/21, 19:27

Commit message

With the history-synchronization introduced in #93988,
window.currentSubScript has been unconditionally overwritten
after loading a new module in the content frame.
This causes an empty currentSubScript string to be stored
for secondary modules (modules not linked in the module menu),
and results in subsequent faults, when currentSubScript
is used to open a different page with the current module context.

Review

  • Code review CR +2

    Imported before Forger kept the single votes, the next import adds them.

  • Verified V +2

    Imported before Forger kept the single votes, the next import adds them.

Issues 2

Files 2