[CTW] Remove COM proxy infrastructure
Categories
(Core :: Disability Access APIs, task)
Tracking
()
Tracking | Status | |
---|---|---|
firefox115 | --- | fixed |
People
(Reporter: Jamie, Assigned: Jamie)
References
(Blocks 1 open bug)
Details
(Whiteboard: [ctw-postship])
Attachments
(5 files)
Once we no longer depend on COM proxies, we can remove all the supporting infrastructure, including HandlerProvider, AccessibleHandler, most of a11y::PlatformInit, GeckoCustom, the installer + MSIX + build system stuff associated with the handler and typelibs, code within ACCESSIBILITY defines in ipc/mscom, WaitForSyncNotifyWithA11yReentry in ipc/glue, and probably more I've missed.
Assignee | ||
Updated•2 years ago
|
Comment 1•2 years ago
|
||
Don't know if it is relevant, but the Thunderbird team should be made aware of this so they know when the handler is to be removed. I don't suspect there will be many issues, especially since TB works better with CTW enabled anyway, even in the ESR version they're using, but they should be made aware anyway that something will de-register the handler with a Firefox update at some point.
Assignee | ||
Comment 2•2 years ago
|
||
Thunderbird has used different UUIDs for the handler for a while now, so this shouldn't break them.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 3•2 years ago
|
||
Assignee | ||
Comment 4•2 years ago
|
||
Assignee | ||
Comment 5•2 years ago
|
||
This includes AccessibleHandler, HandlerProvider and the now unnecessary IAcessible2 COM proxy dll.
Even with the new architecture, we still use IAccessible2, but we no longer need a COM proxy because we aren't using COM across processes ourselves.
If clients want to use IAccessible2 across processes, they're responsible for registering a COM proxy as with all other IAccessible2 applications.
Assignee | ||
Comment 6•2 years ago
|
||
This was only ever used by the old accessibility architecture based on content process COM proxies, which is now being removed.
Assignee | ||
Comment 7•2 years ago
|
||
This actually hasn't ever been used in a shipping build of Firefox.
Although sync IPDL was tried with Windos a11y for a while when e10s was still disabled, it was never feasible and was replaced with COM proxying.
Comment 9•1 years ago
|
||
Backed out for build bustages
Backout link: https://hg.mozilla.org/integration/autoland/rev/f4dd1d973e6af5ff602aedbf4349fef32fe2db3f
Log link: https://treeherder.mozilla.org/logviewer?job_id=416570108&repo=autoland&lineNumber=69478
Assignee | ||
Updated•1 years ago
|
Comment 10•1 years ago
|
||
Comment 11•1 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/c426299b75bc
https://hg.mozilla.org/mozilla-central/rev/6e7c8f403f9b
https://hg.mozilla.org/mozilla-central/rev/9bbf88ecda1d
https://hg.mozilla.org/mozilla-central/rev/52fc00be37e9
https://hg.mozilla.org/mozilla-central/rev/007da88a0da1
https://hg.mozilla.org/mozilla-central/rev/97bab904eba3
Updated•1 years ago
|
Description
•