Closed Bug 238794 Opened 21 years ago Closed 21 years ago

Return (enter) key always triggers next button irrespective of focus in wizard

Categories

(Core :: XUL, defect)

x86
Linux
defect
Not set
trivial

Tracking

()

RESOLVED DUPLICATE of bug 274672

People

(Reporter: P.Edelman, Assigned: bugs)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040207 Firefox/0.8 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040207 Firefox/0.8 When a wizard is created using XUL, pressing the "enter" key always triggers the "next" button in addition to the action for the element which has focus. For example, if a wizardpage only contains a button which opens a file selector, this button is focussed by default. When the "return" key is pressed, a file selector is opened, but the wizard also switches to the next page. The same holds for a multiline textbox which has focus. On "enter", a newline is inserted in the textbox, but also the page is advanced. There is a small difference in firefox 0.8 and mozilla (build 20040325) in this respect. In the first example, in mozilla, the button stays focussed even when the page is advanced, so pressing "enter" on the next page results in the opening of a file selector. This does not happen in firefox which resets the focus on every page advance. Reproducible: Always Steps to Reproduce: 1. Register the testcase in your chrome (otherwise the wizard doesn't work properly) 2. Open this wizard. The button is now selected. 3. Press "Enter". Actual Results: An alert box is displayed, and the wizard also advances to the next page. Expected Results: Only the alert should be displayed.
Not confirming, giving to Ben for sanity check. /be
Assignee: hyatt → bugs
Dupe of bug 274672 which already has a reviewed patch ready. :-) *** This bug has been marked as a duplicate of 274672 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: shrir → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.