Closed Bug 1289850 Opened 8 years ago Closed 6 months ago

Future-proofing mscom ArrayData

Categories

(Core :: Disability Access APIs, defect, P3)

Product:
Core
Component:
Disability Access APIs
Platform:
Unspecified
Windows
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX
Tracking Flags:
Tracking Status
firefox50 --- affected

People

(Reporter: bugzilla, Unassigned)

Details

Right now we have the RegisterArrayData() and the ArrayData struct, which encodes information about array parameters. This approach requires us to enumerate every possible COM interface that we are providing and adding the relevant metadata. It would be nice if we could have a solution that would "just work" without needing to mess with that stuff.

One possibility is to read the Oicf bytecode from the proxy/stub and use that as the canonical source for this information. That's a non-trivial amount of work, however.
setting it as P3: it's something worth to explore, but no activity for a year. Aaron, please feel free to bump the priority if that's a bottleneck for us.
Priority: -- → P3
Severity: normal → S3

No longer relevant with CtW and the old architecture has been removed.

Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.