[Codebridge] Added weblab and pythonlab shortcuts for run button, console, and editor

[hannahbergam]

Adds keyboard shortcuts for the run button (ctrl + r), the editor (ctrl + e) and the console output (ctrl + o) for PythonLab (and the edit shortcut works for Weblab).

I added this in Codebridge so it would work for pythonlab and weblab.

Below is a video! It's a bit hard to follow unless you can see the focus, which I use the shortcuts to move between run button, editor, and output.

This is after hearing from the Maryland School for the Blind kids that they'd like a quicker way to navigate between the most important parts of the page!

I elected to use ctrl + instead of just the letters so that the shortcuts also work from within (and don't interfere with) the text editors (console and workspace editor).

I have a mac, so would appreciate someone testing this on another device!

Screen.Recording.2025-05-14.at.1.22.33.PM.mov

Links

• Jira: https://codedotorg.atlassian.net/browse/SL-1236

Testing story

Deployment strategy

Follow-up work

Privacy

Security

Caching

PR Checklist:

• Tests provide adequate coverage
• Privacy and Security impacts have been assessed
• Code is well-commented
• New features are translatable or updates will not break translations
• Relevant documentation has been added or updated
• User impact is well-understood and desirable
• Pull Request is labeled appropriately
• Follow-up work items (including potential tech debt) are tracked and linked

[sanchitmalhotra126]

If helpful, here is the original PR that added a run shortcut for legacy labs! #55942
Two things:

1. I totally misremembered 🤦 - looks like CTRL+Enter is what we wired up for Run (not CTRL+R)
2. That PR created a KeyHandler util that may be useful here!

[hannahbergam]

If helpful, here is the original PR that added a run shortcut for legacy labs! #55942 Two things:

1. I totally misremembered 🤦 - looks like CTRL+Enter is what we wired up for Run (not CTRL+R)
2. That PR created a KeyHandler util that may be useful here!

ooo thank you! I'll take a look at this handler! Also, I might stick with R considering the rest of the shortcuts are letters... but definitely open to feedback.

[hannahbergam]

If helpful, here is the original PR that added a run shortcut for legacy labs! #55942 Two things:

1. I totally misremembered 🤦 - looks like CTRL+Enter is what we wired up for Run (not CTRL+R)
2. That PR created a KeyHandler util that may be useful here!

ooo thank you! I'll take a look at this handler! Also, I might stick with R considering the rest of the shortcuts are letters... but definitely open to feedback.

@sanchitmalhotra126 How would you feel about me adding a preventDefault() to the keyHandler?

[hannahbergam]

If helpful, here is the original PR that added a run shortcut for legacy labs! #55942 Two things:

1. I totally misremembered 🤦 - looks like CTRL+Enter is what we wired up for Run (not CTRL+R)
2. That PR created a KeyHandler util that may be useful here!

ooo thank you! I'll take a look at this handler! Also, I might stick with R considering the rest of the shortcuts are letters... but definitely open to feedback.

@sanchitmalhotra126 How would you feel about me adding a preventDefault() to the keyHandler?

mmm actually this seems to interfere with the rest of the keyboard events so I'm not sure there is an easy way to utilize this util in PythonLab. I would also have to register both ctrl and command, which I believe would make it just as many lines changed😅 Alright with you if I maintain the current approach?

[sanchitmalhotra126]

mmm actually this seems to interfere with the rest of the keyboard events so I'm not sure there is an easy way to utilize this util in PythonLab. I would also have to register both ctrl and command, which I believe would make it just as many lines changed😅 Alright with you if I maintain the current approach?

Yep, totally fine!