RESOLVED WONTFIX 67912
[Meta] Shadow DOM should be accessible from JavaScript based assistive technology. 
https://bugs.webkit.org/show_bug.cgi?id=67912
Summary [Meta] Shadow DOM should be accessible from JavaScript based assistive techno...
Hayato Ito
Reported 2011-09-11 18:32:24 PDT
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
Comment 1 2011-09-11 19:05:16 PDT
Can you explain why this needs to be in WebKit if it is not exposed to Web content?
Hayato Ito
Comment 2 2011-09-11 19:12:14 PDT
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
Comment 3 2011-09-11 23:33:31 PDT
(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
Comment 4 2011-09-11 23:48:57 PDT
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
Comment 5 2011-09-12 06:25:13 PDT
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?
Note You need to log in before you can comment on or make changes to this bug.