67912 2011-09-11 18:32:24 -0700 [Meta] Shadow DOM should be accessible from JavaScript based assistive technology. 2011-09-12 06:25:13 -0700 1 1 1 Unclassified WebKit Accessibility 528+ (Nightly build) Unspecified Unspecified RESOLVED WONTFIX P2 Normal --- 63606 66669 1 hayato webkit-unassigned ap sam shinyak oldest_to_newest 465436 0 hayato 2011-09-11 18:32:24 -0700 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. 465444 1 sam 2011-09-11 19:05:16 -0700 Can you explain why this needs to be in WebKit if it is not exposed to Web content? 465445 2 hayato 2011-09-11 19:12:14 -0700 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? 465506 3 sam 2011-09-11 23:33:31 -0700 (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? 465507 4 hayato 2011-09-11 23:48:57 -0700 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? 465580 5 hayato 2011-09-12 06:25:13 -0700 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?