Fix Shift + L not working in stdin

[krassowski]

References

Fixes #15429

Code changes

Adds selector that should have been added before.

User-facing changes

When input box is focused, shift + l types "L" rather than toggling line numbers

Backwards-incompatible changes

None

[jupyterlab-probot]

Thanks for making a pull request to jupyterlab!
To try out this branch on binder, follow this link:

[krassowski]

One failure is relevant:

  4) [jupyterlab] › test/jupyterlab/shortcuts.test.ts:29:5 › Shortcuts must be unique ──────────────

    Error: expect(received).toEqual(expected) // deep equality

    - Array []
    + Array [
    +   "Skipping this default shortcut because it collides with another default shortcut. {command: viewmenu:line-numbering, keys: Array(1), selector: .jp-Notebook.jp-mod-commandMode :focus:not(:read-write)}",
    + ]

Removing notebook:toggle-all-cell-line-numbers appears to fixing without regressions on the UI.

[krassowski]

The failing visual regression test:
[jupyterlab] › test/jupyterlab/kernel.test.ts:108:9 › Kernel › Console › Should not ask kernel when creating console from launcher
is addressed by #15355

[fcollonval]

Thanks @krassowski

[fcollonval]

@meeseeksdev please backport to 4.0.x

[lumberbot-app]

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout 4.0.x
git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 8405524535e761338e1b73ed93f8e7cda8d3d7fc

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #15440: Fix Shift + L not working in stdin'

4. Push to a named branch:

git push YOURFORK 4.0.x:auto-backport-of-pr-15440-on-4.0.x

5. Create a PR against branch 4.0.x, I would have named this PR:

"Backport PR #15440 on branch 4.0.x (Fix Shift + L not working in stdin)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.