"ASSERTION: Can't create an accessible for the document!" with pagehide event abuse

RESOLVED WORKSFORME

Status

()

Core
Disability Access APIs
RESOLVED WORKSFORME
5 years ago
3 months ago

People

(Reporter: Jesse Ruderman, Unassigned)

Tracking

(Blocks: 1 bug, {assertion, testcase})

Trunk
x86_64
Mac OS X
assertion, testcase
Points:
---
Bug Flags:
in-testsuite +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
Created attachment 764032 [details]
testcase

With accessibility enabled, the testcase hits:

###!!! ASSERTION: Can't create an accessible for the document!: 'parentDocAcc', file accessible/src/base/DocManager.cpp, line 389
Blocks: 888531
We should fix some day, but seems just case of we've torn down docunment and then somebody adds stuff to DOM.    Probablynot too important.
No longer blocks: 888531

Comment 2

4 years ago
(In reply to Trevor Saunders (:tbsaunde) from comment #1)
> We should fix some day, but seems just case of we've torn down docunment and
> then somebody adds stuff to DOM.    Probablynot too important.

what would a fix look like? just remove an assertion or a11y logic changes?
(In reply to alexander :surkov from comment #2)
> (In reply to Trevor Saunders (:tbsaunde) from comment #1)
> > We should fix some day, but seems just case of we've torn down docunment and
> > then somebody adds stuff to DOM.    Probablynot too important.
> 
> what would a fix look like? just remove an assertion or a11y logic changes?

haven't investigated enough to be sure, but removing the assert doesn't sound totally crazy.

Comment 4

4 years ago
I think I see this assertion in a real life and it's annoying. I'd be good either fix the problem or remove it.
(In reply to alexander :surkov from comment #4)
> I think I see this assertion in a real life and it's annoying. I'd be good
> either fix the problem or remove it.

I didn't say *you* shouldn't care :-p

The no frame for text getting one gets hit a lot more often for me and annoys me a lot more.
Flags: needinfo?(ryanvm)
This still asserts when e10s is disabled, but doesn't with e10s enabled. Per discussion with eeejay, I'm just going to call this bug WFM at this point and land the testcase as a crashtest since e10s isn't far away from being the only supported mode anyway.
Status: NEW → RESOLVED
Last Resolved: 3 months ago
Flags: needinfo?(ryanvm) → in-testsuite+
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.