Closed
Bug 1061332
Opened 10 years ago
Closed 1 year ago
Key press event is triggering even when there is alert box/confirmation box prompted
Categories
(Core :: DOM: UI Events & Focus Handling, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: pawangupta.iu, Unassigned)
Details
(Whiteboard: DUPEME)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 (Beta/Release) Build ID: 20140716183446 Steps to reproduce: I have bound a key press event on the text box. So that when user presses an enter key the cursor will move from one text box to another. But if user enters some wrong value then i've put an alert message and return false from that function. Actual results: If user enters some wrong value then there will be an alert box displayed. But at If user presses enter key on alert message to click on OK then the cursor automatically moves from one text box to another. Expected results: In ideal case this key press event should not trigger when there is a alert box or confirmation box prompted in the browser. So that the focus stays on the text box for which the same alert message is displayed.
Reporter | ||
Updated•10 years ago
|
Severity: normal → major
Component: General → Event Handling
Priority: -- → P1
Comment 1•10 years ago
|
||
Please provide a minimal test case and attached here. (And do not touch Importance Priority)
Flags: needinfo?(pawangupta.iu)
Priority: P1 → --
Updated•10 years ago
|
Whiteboard: DUPEME
Updated•9 years ago
|
Flags: needinfo?(pawangupta.iu)
Assignee | ||
Updated•5 years ago
|
Component: Event Handling → User events and focus handling
Comment 2•1 year ago
|
||
In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.
Severity: major → --
Comment 3•1 year ago
|
||
Close as INCOMPLETE since there is no valid test case to reproduce the issue.
Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•