1348148 - fix assertion failure in Accessible::HandleAccEvent() that there is an ipc doc

Status: RESOLVED FIXED

(Core :: Disability Access APIs, enhancement)

Description

[Trevor Saunders (:tbsaunde)]

It is awkward to need to have a DocAccessibleChild to send events with before
DocAccessible::DoInitialUpdate() is called because we might not have a
TabParent for the document until then.  However we could try to fire reload
events on documents before DoInitialUpdate() was called which would require
having a DocAccessibleChild there to send the load event to the parent process.

However before DocAccessible::DoInitialUpdate() is called the document already
has a pending load event.  If a document hasn't yet been the subject of a load
event it doesn't make a lot of sense to fire a reload event for that document,
      and then the initial load event.  So it should be safe to skip firing
      reload events for documents where mLoadEvent specifies a load event to
      fire in the future.

Comment 1

[Trevor Saunders (:tbsaunde)]

Attachment: try and avoid firing load events on unloaded documents

Comment 2

[alexander :surkov (:asurkov)]

(In reply to Trevor Saunders (:tbsaunde) from comment #0)
> If a document hasn't yet been the subject of a
> load
> event it doesn't make a lot of sense to fire a reload event for that
> document,
>       and then the initial load event.  So it should be safe to skip firing
>       reload events for documents where mLoadEvent specifies a load event to
>       fire in the future.

you should put comments like this right into the code.

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/5a08bfa91d2b
try and avoid firing load events on unloaded documents r=davidb

Comment 4

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/5a08bfa91d2b