Closed Bug 434681 Opened 17 years ago Closed 14 years ago

###!!! ASSERTION: Creating accessible for node with no document: 'content->GetDocument()', file nsAccessibilityService.cpp, line 1379

Categories

(Core :: Disability Access APIs, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: surkov, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

Attached file mochitest based test
###!!! ASSERTION: Creating accessible for node with no document: 'content->GetDocument()', file nsAccessibilityService.cpp, line 1379 we'll get the assertion when the sequence of action is fulfilled: 1) add text nodes to text accessible 2) remove text accessible the reason, we try to fire text events for the node that isn't in document already.
Probably we should have more strong rules in nsAccEvent::ApplyEventRules and exclude un actual events.
Attached patch wipSplinter Review
fixed testcase but issue is still valid for www.webmd.com where tabs are changed dynamically. There I get many 'create' events and preceding them reorder event.
Blocks: eventa11y
I'm getting a LOT of these warnings on www.spike.com. In fact the debug trunk build is unusable... and the warnings never end. Tested with NVDA 2009.1.
Blocks: 571613
The example is not valid anymore since Gecko architecture was changed: we process element insertion after timeout. I don't see this assertion in mochitest long, also I don't see it when I run spike.com with NVDA. Closing as worksforme.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: