my .xsession-errors log is still flooded with the same error signal name 'load_complete' is invalid for instance '0x7fcb46e0d230' of type 'MaiAtkType139'
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox98 | --- | fixed |
People
(Reporter: beacon, Assigned: Jamie)
References
Details
Attachments
(1 file)
Many entries in .xsession-errors log
signal name 'load_complete' is invalid for instance '0x7fcb46e0d230' of type 'MaiAtkType139'
|
Assignee | |
Comment 1•2 years ago
|
||
Fix note: This object doesn't have the document interface. My guess is that we're firing a doc load complete for an ARIA document or dialog, but load_complete is only valid on the ATK document interface (which ARIA documents don't have). We should not fire this signal if the object isn't a real document.
|
|
Assignee | |
Comment 2•2 years ago
|
||
In Gecko, ARIA documents and dialogs can fire load complete/reload/load stopped events, but they don't support AtkDocument.
Since the corresponding ATK signals are only supported on AtkDocument, just ignore these events for anything which isn't a DocAccessible.
This has no impact on clients, since the signal was invalid anyway, but it does prevent errors being logged.
|
||
Updated•2 years ago
|
Pushed by jteh@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ba9fe110718c Don't emit load_complete, reload and load_stopped signals on objects that don't support AtkDocument. r=eeejay
|
||
Comment 4•2 years ago
|
||
| bugherder | ||
Description
•