Closed Bug 1641002 Opened 5 years ago Closed 5 years ago

Implement base class and protocol to abstract apple methods

Categories

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

Unspecified
macOS
defect

Tracking

()

RESOLVED FIXED
mozilla78
Tracking Status
firefox78 --- fixed

People

(Reporter: eeejay, Assigned: eeejay)

References

Details

(Whiteboard: [mac2020_1])

Attachments

(2 files)

From bug 1637076:

(1) We should write a new protocol that our base class and additional (sub) classes will implement. This protocol should define a set of required methods and properties for each accessible type, and a set of optional methods and properties that accessibles may implement as needed to communicate which selectors/attributes/actions, etc they support. This protocol should be named with the convention mozAccessibleProtocol, assuming our base class is still mozAccessible.

This bug will tackle this first item by implementing a base class and an inner protocol for subclasses to implement as needed.

A followup bug will be for actually refactoring the subclasses and make them use tthe inner protocol.

This sets up the possibility of moving most non-gecko things to a base class, and
start a protocol to add for all the subclasses to implement as needed.

Add most attributes getters, setters and actions to prottocol,
autogenerate objective c dictionaries, and implement forwarding
logic from NSAccessibility methods.

Depends on D76920

Pushed by eisaacson@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/2d0bbd99d887 Introduce MOXAccessible protocol and MOXAccessibleBase. r=morgan https://hg.mozilla.org/integration/autoland/rev/7afbfa63f937 Map NSAccessibility API to MOXAccessible protocol. r=morgan
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla78
Regressions: 1706910
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: