Bug 67912
| Summary: | [Meta] Shadow DOM should be accessible from JavaScript based assistive technology. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Hayato Ito <hayato> |
| Component: | Accessibility | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | ap, sam, shinyak |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | 63606 | ||
| Bug Blocks: | 66669 | ||
Hayato Ito
Provide a JavaScript API to access shadow DOM so that JavaScript-based assistive technology like ChromeVox can access user-created Shadow DOM.
We should be careful so that this API can only be accessed by privileged extensions, not any page.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Sam Weinig
Can you explain why this needs to be in WebKit if it is not exposed to Web content?
Hayato Ito
You are right. I expect we don't need to do anything except for depending bugs in WebKit side.
https://bugs.webkit.org/show_bug.cgi?id=63606
I'd just like to track all dependent bugs using this issue.
(In reply to comment #1)
> Can you explain why this needs to be in WebKit if it is not exposed to Web content?
Sam Weinig
(In reply to comment #2)
> You are right. I expect we don't need to do anything except for depending bugs in WebKit side.
> https://bugs.webkit.org/show_bug.cgi?id=63606
>
> I'd just like to track all dependent bugs using this issue.
I don't understand why this bug exists if there is nothing to do and no API you plan on exposing. Should the bug be renamed?
Hayato Ito
Hi Sam,
Thank you for the comment.
I agree the title of this bug is confusing. I've renamed it.
Let me continue investigating whether the current planned Shadow DOM APIs is good enough or not in WebKit side. I'll update this bug later.
(In reply to comment #3)
> (In reply to comment #2)
> > You are right. I expect we don't need to do anything except for depending bugs in WebKit side.
> > https://bugs.webkit.org/show_bug.cgi?id=63606
> >
> > I'd just like to track all dependent bugs using this issue.
>
> I don't understand why this bug exists if there is nothing to do and no API you plan on exposing. Should the bug be renamed?
Hayato Ito
I'd like to mark this issue WONTFIX.
Such accessibility JavaScript APIs should be provided in more upper layers, like Chrome Extension APIs or something similar, instead of WebCore and its bindings.
(In reply to comment #4)
> Hi Sam,
> Thank you for the comment.
>
> I agree the title of this bug is confusing. I've renamed it.
> Let me continue investigating whether the current planned Shadow DOM APIs is good enough or not in WebKit side. I'll update this bug later.
>
> (In reply to comment #3)
> > (In reply to comment #2)
> > > You are right. I expect we don't need to do anything except for depending bugs in WebKit side.
> > > https://bugs.webkit.org/show_bug.cgi?id=63606
> > >
> > > I'd just like to track all dependent bugs using this issue.
> >
> > I don't understand why this bug exists if there is nothing to do and no API you plan on exposing. Should the bug be renamed?