Closed Bug 761093 Opened 12 years ago Closed 12 years ago

Key events fired by mozbrowser is fired from parent frame window, going through target phase only

Categories

(Core :: DOM: Core & HTML, defect)

Product:
Core
Component:
DOM: Core & HTML
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 755648

People

(Reporter: timdream, Unassigned)

Details

These key events should fired from the <iframe> generated the event.
If that's not possible, consider firing from <html>, i.e. |document.documentElement|.

Regular browser, e.g. Firefox, fires the key events on the focused element. When you click on the empty webpage, <body> gets the focus. When you press TAB and navigate through the Firefox UI and the web page, sometimes <html> gets the focus. BUT NEVER |window|.

I am working on reorganizing the Gaia System app, to make it work I would need the ability to cancel an bubbling event handler that is bound before a capturing event handler. If both event handler get executed at the desired phase, this will work, but with window-firing events, both will get executed on the target phase and the capturing event handler cannot cancel the bubbling event handler as it will execute first.
The described was implemented in bug 757486.
I do not understand what you are trying to say here.
The event is fired to the <iframe> element and when you are getting the event from a parent mozbrowser, to prevent it from bubbling more, you have to call |event.preventDefault();|.
Yeah, this should be caused by my pending patch in buy 755648 ... since I am working on SLEEP button and bug 757486 doesn't handle sleep buttons.
No longer depends on: 757764, 757486, 759017
The current shell.js suffers the same issue. Will fix this along the way in bug 755648.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.