Closed
Bug 1826868
Opened 2 years ago
Closed 2 years ago
[CtW][tail-end] Sync call RemoteAccessible::Title() is still used in XPCOM and MacOS
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
FIXED
115 Branch
Tracking | Status | |
---|---|---|
firefox115 | --- | fixed |
People
(Reporter: eeejay, Assigned: eeejay)
References
Details
Attachments
(1 file)
A non sync or cache alternative should be used.
Updated•2 years ago
|
Severity: -- → S3
Assignee | ||
Comment 1•2 years ago
|
||
Looks like this is also used in MacOS.
Summary: [CtW][tail-end] Sync call RemoteAccessible::Title() is still used in XPCOM → [CtW][tail-end] Sync call RemoteAccessible::Title() is still used in XPCOM and MacOS
Comment 2•2 years ago
|
||
Hmm. I think we have two "Title"s here.
- For XPCOM, there's xpcAccessibleDocument::Title. However, that is only supported for local documents (DocAccessible). For remote documents, it will return NS_ERROR_FAILURE. I don't think we really need to support this at all, so we could just drop this method in future. Right now, though, I don't think we need to do anything; it's only used in one test.
- The real concern here is Mac. RemoteAccessible::Title isn't referring to document title, but seems to have something to do with headings and flattening their text content. I don't quite understand what this is for. Why isn't Name enough?
Flags: needinfo?(eitan)
Assignee | ||
Comment 3•2 years ago
|
||
The message wasn't doing anything useful on Mac. Took the opportunity to
correcty expose the AXTitle/AXDescription of headings.
Updated•2 years ago
|
Assignee: nobody → eitan
Status: NEW → ASSIGNED
Pushed by eisaacson@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/02aadba5c38a
Remove useless Title IPC sync message. r=morgan,ipc-reviewers,mccr8
Comment 5•2 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox115:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 115 Branch
Assignee | ||
Updated•8 months ago
|
Flags: needinfo?(eitan)
You need to log in
before you can comment on or make changes to this bug.
Description
•