Bug 245546
| Summary: | AX: Consider whether AXIsSuggestedDeletion/Insertion should not use "Suggested" (Google API comment) | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | James Craig <jcraig> |
| Component: | Accessibility | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | andresg_22, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | All | ||
| OS: | All | ||
James Craig
AX: Consider whether AXIsSuggestedDeletion/Insertion should not use "Suggested" (Google API comment)
Aaron Leventhal (accessibility implementer for Google/Chromium) suggested the API AXIsSuggestedDeletion/Insertion is misleading, as the insertions/deletions sometimes refer to version changes that have already been accepted, and other non-suggestion diffs.
Apple internal discussion consensus was:
- yes, we should change it
- its low priority though, so probably not this release
- keep the legacy API key working in perpetuity, so we don't break implementations that adopt the "Suggested" version in the meantime.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/100299930>
James Craig
A little more info here: https://github.com/w3c/core-aam/pull/137
To whichever WebKit engineer implements this change, please file (or ask me to file) a new issue against Core-AAM to update the mapping: https://github.com/w3c/core-aam/issues/new/choose Thanks.