In order to get keybinding limping, we need an API for getting the content node that currently has focus.

Setting the target milestone to M4 since we really need this for M4. Sorry Tom!

i.e., we need for events to bubble/be capturable from child frames to parents.

Well, we need that too, but first we need to be able to get the focused frame in the first place.

Changing description as per discussion today. I think adding a direct 'what's focused' api will not solve this. What we really need is a way to get events from subframes. This can be accomplished either by adding bubbling through frames (keeping in mind this goes beyond the current DOM spec and if later standardized behavior contradicts this we got trouble) or we can find another way to get these events internally. Having looked at the code I'm a little uncomfortable putting in this new event link right before M4. If we really need it I will but given the choice I'd like to play with it for a while. But I'll put it up for a vote here as to whether to move this to M5.

If you're uncomfortable with it, I say M5. I'd rather keep things stable.

Dropping this to M5 to give us a little while to pound on it and checks its stability.

Moving off M5 radar since Tom is out of town.

Well the critical part of this, receiving events from the content area is okay. And additional part of this bug still exists with nested framesets but its less critical. Moving to M7.

With the event capturing system and some hookups provided by hyatt you can now get events from subframes *IF* you are the chrome. Still discussing what the content area should do for backwards compatibility but I think the immediate problems are solved. Pushing way down on milestone list to look at later.

I'm going to mark this fixed unless someone has a strong need for more than we have now.

verified