| Summary: | [terminal] typing '?' character brings up key bindings list | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Chris McGee <sirnewton_01> |
| Component: | Docker | Assignee: | Anthony Hunter <ahunter.eclipse> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ahunter.eclipse, ken_walker, Silenio_Quarti |
| Version: | 5.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Chris McGee
Students are finding the same thing in their Orionode work. Likely the text area changes the shortcut somehow. Hi Silenio, is there a way to turn on a key binding when a particular div is active? I believe the command framework is supposed to detect that the widget in focus is TEXTAREA, INPUT, contentedtiable, etc. and not run commands associated with content keys (?, a, b, etc). Is the input on the terminal not done with on of those element types? (In reply to Silenio Quarti from comment #3) > I believe the command framework is supposed to detect that the widget in > focus is TEXTAREA, INPUT, contentedtiable, etc. and not run commands > associated with content keys (?, a, b, etc). Is the input on the terminal > not done with on of those element types? Correct, the terminal is just a bunch of nested div with a bunch of styles applied. Maybe there is a style I can add to the outer dev? I do not think there is anything you can add now. Take a look at commands.js#189. The code only checks the node tagName. Maybe we can add a specific CSS class to the node in focus and commands.js checks its presence. We have removed the terminal feature from Orion 8.0, see Bug 457990 for full details. |