526313 - Focus event for editable iframe is inconsistent

Status: NEW

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

Description

[David Bolter [:davidb] (NeedInfo me for attention)]

This is a spin off from bug 512059. We'll probably take a work around there, but I want to understand how bug 512059 comment 27 happens:

"I took another look at this today with fresh eyes. In
nsRootAccessible::FireAccessibleFocusEvent we call nsAccessNode's
GetCurrentFocus. The first time the content editable is focused, we get back an
nsIDOMWindow from GetCurrentFocus. Subsequent times the content editable is
focused we get back an nsIDOMElement (with local name "HTML").

I don't yet know why.

The subsequent times, this nsIDOMelement we get is not the same object as the
node passed into FireAccessibleFocusEvent so we bail, assuming that there will
be a subsequent focus event for the real focus. The comments in the code say
this is about suppressing document focus because real DOM focus will happen
next."

Comment 1

[alexander :surkov (:asurkov)]

David, could you clarify please what should we fix here? You don't like we get sometimes focused window and sometimes focused node? If this is a bug and you think we shouldn't handle this in accessible module then why is this bug targeted to accessible module?

Comment 2

[David Bolter [:davidb] (NeedInfo me for attention)]

I think this is a bug in focus management or editor, but I need to investigate again before I can describe the problem properly. I don't know/when if I'll have time.

Comment 3

[alexander :surkov (:asurkov)]

Ok, let's move it to more proper component. If I understand right then the bug is focus manager GetFocusedElementForWindow returns inconsistent results as described in comment #0.

Also in bug 673958 I noticed similar behavior:

in the case of editable iframe@src="about:blank" (i.e. iframe.contentDocument.designMode="on") the DOM focus event is fired for DOM document and window but nsFocusManager::GetFocusedContent() returns HTML element (document root element) and there's no DOM focus event for the HTML element.

Neil commented in bug 673958 comment #12 that GetFocusedContent() should probably return null in this case.

Unblocking bug 375743 since we don't really depend on this behavior after bug 673958 is fixed.

Comment 4

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven't been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.