Bug 121577
| Summary: | Correctly handle control labels inside canvas fallback content | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ryosuke Niwa <rniwa> |
| Component: | Accessibility | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | cfleizach, jcraig, webkit-bug-importer |
| Priority: | P2 | Keywords: | BlinkMergeCandidate, InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Ryosuke Niwa
Consider merging https://chromium.googlesource.com/chromium/blink/+/ae817d4f6eb0ab938a8586775902ff24872aa217
The code changes are trivial, just moving code from
AccessibilityRenderObject to AccessibilityNodeObject,
with trivial changes to make the code work there.
Elements inside canvas fallback content are not rendered
but are otherwise accessible; eventually we should move as
much logic as possible to AccessibilityNodeObject so that
there are few differences between inside of a canvas and
outside for accessibility.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/15024761>
chris fleizach
This is something we want to do as well. Don't know if a direct merge is possible or not. I think I see other code divergences in these methods