Closed Bug 708196 Opened 13 years ago Closed 8 years ago

Editable trees: Home and End keys don't work in edit mode

Categories

(Core :: XUL, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jwkbugzilla, Unassigned)

References

Details

(Keywords: regression, testcase)

Attachments

(1 file)

Steps to reproduce: 1. Use Remote XUL Manager (https://addons.mozilla.org/addon/remote-xul-manager/) to allow remote XUL on bugzilla.mozilla.org. Alternatively, you can set dom.allow_XUL_XBL_for_file preference to true but then you will need to download the testcase and open it from file://. 2. Open attachment 235591 [details] in the browser. 3. Double click the first cell to start editing. 4. Press Home key, then End key. Actual results: Nothing happens when the keys are pressed, the entire text is still selected. Expected results: Selection disappears and caret moves to the start of the text when Home is pressed, then it moves to the end of the text when End is pressed. This is apparently a regression given that bug 350333 fixed this behavior. Right now I have to use the following hack in Adblock Plus to make sure things work as expected: > treeElement.inputField.addEventListener("keypress", function(event) > { > // Prevent the tree from capturing cursor keys pressed in the input field > if (event.keyCode >= event.DOM_VK_PAGE_UP && event.keyCode <= event.DOM_VK_DOWN) > event.stopPropagation(); > }, false);
This behavior can be observed both in Firefox 8 and current 11.0a1 nightly builds.
Version: unspecified → Trunk
Hi, The testcase you provided is no longer available. Can you please provide another one so I can test on my end? Also, is this still reproducible on your end ? If yes, can you please retest this using latest FF release and latest Nightly build (https://nightly.mozilla.org/) and report back the results ? When doing this, please use a new clean Firefox profile, maybe even safe mode, to eliminate custom settings as a possible cause (https://goo.gl/PNe90E). Thanks
Flags: needinfo?(trev.moz)
Attaching an extension as testcase. Steps to reproduce are now: 1. Install the attached extension (go to about:config and set xpinstall.signatures.required pref to false if necessary, the extension is unsigned). 2. Type "chrome://test/content/test.xul" in the address bar (without quotation marks). 3. Double click the first cell to start editing. 4. Press Home key, then End key.
Flags: needinfo?(trev.moz)
I can no longer reproduce this issue, works as expected in Firefox 47 on both Windows and Mac OS X.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: