Closed Bug 1259715 Opened 10 years ago Closed 6 years ago

After adding an <a> node by setting innerHTML, immediately clicking it by getElementById().click() failed

Categories

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

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

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: jhao, Unassigned)

References

(Depends on 1 open bug)

Details

This bug is the follow-up bug of Bug 1241634. In test case dom/security/mixedcontentblocker/test_frameNavigation.html, when we navigate a grandchild https page to an http page when it is embedded in http pages, sometimes the navigation will fail. A work-around is found by adding a 0-millisecond setTimeout. We will use the work-around to enable that test, but also track the underlying issue by this bug.
Depends on: 1265068

I suspect the real issue is not the innerHTML bit but whether the frame containing that element has a prescontext or not. See bug 1218456 comment 8. I expect that fixing that would fix this issue too.

Depends on: 1218456

Should be fixed by the fix in bug 1218456.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.