Open Bug 1053953 Opened 10 years ago Updated 2 years ago

No caret events fired on unclosed iframe document with javascript: URL

Categories

(Core :: Disability Access APIs, defect)

x86_64
Windows 8.1
defect

Tracking

()

People

(Reporter: Jamie, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

Attached file Test case.
Str:
1. Open the attached test case.
2. Wait 1 second.
Expected: The caret moves to the second character in the paragraph and a caret event is fired.
Actual: The caret moves to the second character in the paragraph, but no caret event is fired.

Note that if you uncomment doc.close() or comment out the iframe.src line, it works as expected.
Blocks: eventa11y
Might be closely related to bug 1053942.
we don't fire any events until document is loaded
As illustrated by this second test case, it's also possible to reproduce this without calling document.open() by instead assigning to document.body.innerHTML. This one is actually more problematic because while you can argue that it's author error to call document.open() without calling document.close(), there is no such argument in this case.
(In reply to alexander :surkov from comment #2)
> we don't fire any events until document is loaded
Given that these test cases demonstrate that there are cases where a non-screen reader user can quite happily interact with a "busy" document, can this be changed so we do get events for busy documents?
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: