Add interface blocking to LazyInstantiator

NEW
Unassigned

Status

()

Core
Disability Access APIs
P2
normal
5 months ago
3 months ago

People

(Reporter: aklotz, Unassigned)

Tracking

Trunk
Unspecified
Windows
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 months ago
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.
I'd like to see this fixed. I wonder if anyone not Aaron can help?
Flags: needinfo?(jmathies)
Priority: -- → P2
Flags: needinfo?(surkov.alexander)

Comment 2

3 months 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

3 months 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)
You need to log in before you can comment on or make changes to this bug.