Closed
Bug 748823
Opened 12 years ago
Closed 10 years ago
Pressing VK_HOME should cycle between absolute start of line and first character of line.
Categories
(DevTools :: Source Editor, enhancement, P4)
DevTools
Source Editor
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cedricv, Unassigned)
References
Details
(Whiteboard: [sourceeditor][orion])
Pressing VK_HOME jumps caret to absolute start of line (row 0). Pressing VK_HOME a second time should jump caret right before the first character on that line (if any).
| Reporter | ||
Comment 1•12 years ago
|
||
As a second thought, the first VK_HOME press should jump to the first character of the line (if any) and the second press should jump to row 0 of line.
| Reporter | ||
Comment 2•12 years ago
|
||
s/first character/first non-whitespace character
Updated•12 years ago
|
Whiteboard: [sourceeditor]
| Reporter | ||
Comment 3•12 years ago
|
||
Is this a feature to implement in SourceEditor or upstream (Orion) ?
Comment 4•12 years ago
|
||
(In reply to Cedric Vivier [:cedricv] from comment #3) > Is this a feature to implement in SourceEditor or upstream (Orion) ? Either way. We can open an upstream bug for this and see where we get.
Comment 5•12 years ago
|
||
Reported upstream: https://bugs.eclipse.org/bugs/show_bug.cgi?id=381682 Thanks for your report Cedric!
Severity: normal → enhancement
Priority: -- → P4
Comment 6•12 years ago
|
||
This is now fixed upstream. The next Orion update should include this fix.
Depends on: 759351
Whiteboard: [sourceeditor] → [sourceeditor][orion]
Comment 7•11 years ago
|
||
Moving to Source Editor component. Filter on CHELICERAE.
Component: Developer Tools → Developer Tools: Source Editor
Comment 8•11 years ago
|
||
This is fixed upstream, but not in the textview component we use. Postponing this fix for a later time.
No longer depends on: 759351
Looks like it works to me, thanks to CM.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(cedricv)
Resolution: --- → FIXED
Updated•5 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•