Open
Bug 1381935
Opened 7 years ago
Updated 2 years ago
Add interface blocking to LazyInstantiator
Categories
(Core :: Disability Access APIs, enhancement, P3)
Tracking
()
NEW
People
(Reporter: bugzilla, Unassigned)
Details
Some a11y instantiators might query for interfaces that we don't support. Unfortunately they have to start a11y to make those queries. If we added a filter to LazyInstantiator's QueryInterface, we could preemptively return E_NOINTERFACE on those ones that we know for sure we do not support. We could also add telemetry for any QIs that forced instantiation but were for unsupported interfaces.
Comment 1•7 years ago
|
||
I'd like to see this fixed. I wonder if anyone not Aaron can help?
Flags: needinfo?(jmathies)
Priority: -- → P2
Updated•7 years ago
|
Flags: needinfo?(surkov.alexander)
Comment 2•7 years ago
|
||
I don't have the cycles for this myself but I'll keep on eye on it. I also don't have any free hands on the team right now.
Flags: needinfo?(jmathies)
Comment 3•7 years ago
|
||
I'd be indeed curious to see a percent of accessibility instantiations by clients requesting unsupported interfaces. I'm not sure though about a technical side here, iirc WM_GETOBJECT always returns IAccessible interface, which assumes accessibility is running.
Flags: needinfo?(surkov.alexander)
Comment 4•6 years ago
|
||
Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•