Closed
Bug 1838138
Opened 2 years ago
Closed 2 years ago
[CTW] Remove InSendMessageEx hack
Categories
(Core :: Disability Access APIs, task)
Tracking
()
RESOLVED
FIXED
116 Branch
| Tracking | Status | |
|---|---|---|
| firefox116 | --- | fixed |
People
(Reporter: Jamie, Assigned: Jamie)
References
Details
(Whiteboard: [ctw-postship])
Attachments
(1 file)
In the old architecture where we had COM proxies to content process Accessibles, we needed an InSendMessageEx hack for some clients other than NVDA (particularly JAWS) to prevent RPC_E_CANTCALLOUT_ININPUTSYNCCALL errors. Now that we no longer use COM proxies (all our COM objects are real objects in the parent process), this hack is no longer necessary and can be removed.
| Assignee | ||
Comment 1•2 years ago
|
||
This was only necessary when we had cross-process COM proxies for accessibility.
Pushed by jteh@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/25b7d7779f41
Remove InSendMessageEx hack. r=nlapre
Comment 3•2 years ago
|
||
Backed out for causing bp-nu bustages in Compatibility.cpp.
- Backout link
- Push with failures
- Failure Log
- Failure line: /builds/worker/checkouts/gecko/accessible/windows/msaa/Compatibility.cpp(105,3): error: use of undeclared identifier 'CrashReporter'
Flags: needinfo?(jteh)
| Assignee | ||
Updated•2 years ago
|
Flags: needinfo?(jteh)
Pushed by jteh@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a5f61c0fd441
Remove InSendMessageEx hack. r=nlapre
Comment 5•2 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox116:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 116 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•