Closed
Bug 1248167
Opened 8 years ago
Closed 8 years ago
Cmd+Delete deletes entire line of text
Categories
(Core :: Widget: Cocoa, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 420669
People
(Reporter: celtic.minstrel.ca, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:43.0) Gecko/20100101 Firefox/43.0 Build ID: 20160105164030 Steps to reproduce: Place the insertion point in the middle of the line of text in an editable text field. (It also occurs in the address bar and the search field.) Then press Cmd+Delete. (The Windows equivalent would be Ctrl+Backspace, though I'm not certain this has the same implication on Windows as it does on OSX.) Actual results: The line containing the insertion point becomes blank (everything except the newline is deleted). (Or, the address bar or search bar is entirely cleared.) Expected results: Only the text from the beginning of the line to the insertion point should be deleted. This is what TextEdit does, and it's generally what I expect from a Mac application. For bonus points, Cmd+FwdDel could provide the reverse - delete from insertion point to end of line. TextEdit doesn't do this, but some other programs (eg TextWrangler, possibly XCode) do.
Reporter | ||
Updated•8 years ago
|
Severity: normal → minor
OS: Unspecified → Mac OS X
Hardware: Unspecified → x86
Ctrl+Backspace key delete a word on Windows at least.
Severity: minor → normal
Component: Untriaged → Widget: Cocoa
Product: Firefox → Core
Reporter | ||
Comment 2•8 years ago
|
||
Ah yes... the OSX equivalent for that is Alt+Delete (where Delete is equivalent to Backspace), which works correctly. Windows probably doesn't have an equivalent, then. (Shift+Home followed by Backspace would get the same effect, and in fact the equivalent on OSX - Shift+Cmd+Left followed by Backspace - does work. Which shouldn't be surprising.)
Comment 3•8 years ago
|
||
Thanks for the report! This is a known bug, marking it as such.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•