Exposes datetime attribute.

content/browser/accessibility/browser_accessibility_win.cc

Index: content/browser/accessibility/browser_accessibility_win.cc
diff --git a/content/browser/accessibility/browser_accessibility_win.cc b/content/browser/accessibility/browser_accessibility_win.cc
index 6866ca987cf702d1326e51bc20a79c2c27a60062..3c79052a320f42a5f8180a3876a2e345f5f7f9cd 100644
--- a/content/browser/accessibility/browser_accessibility_win.cc
+++ b/content/browser/accessibility/browser_accessibility_win.cc
@@ -3173,8 +3173,6 @@ void BrowserAccessibilityWin::UpdateStep1ComputeWinAttributes() {
 
   // Expose the "display" and "tag" attributes.
   StringAttributeToIA2(ui::AX_ATTR_DISPLAY, "display");
-  StringAttributeToIA2(ui::AX_ATTR_DROPEFFECT, "dropeffect");
-  StringAttributeToIA2(ui::AX_ATTR_TEXT_INPUT_TYPE, "text-input-type");
   StringAttributeToIA2(ui::AX_ATTR_HTML_TAG, "tag");
   StringAttributeToIA2(ui::AX_ATTR_ROLE, "xml-roles");
 
@@ -3199,9 +3197,6 @@ void BrowserAccessibilityWin::UpdateStep1ComputeWinAttributes() {
   BoolAttributeToIA2(ui::AX_ATTR_LIVE_ATOMIC, "atomic");
   BoolAttributeToIA2(ui::AX_ATTR_LIVE_BUSY, "busy");
 
-  // Expose aria-grabbed attributes.
-  BoolAttributeToIA2(ui::AX_ATTR_GRABBED, "grabbed");
-
   // Expose container live region attributes.
   StringAttributeToIA2(ui::AX_ATTR_CONTAINER_LIVE_STATUS,
                        "container-live");
@@ -3407,6 +3402,28 @@ void BrowserAccessibilityWin::UpdateStep1ComputeWinAttributes() {
     win_attributes_->ia2_attributes.push_back(L"valuetext:" + GetValueText());
   }
 
+  // Expose dropeffect attribute.

[dmazzoni, 2015/06/09 16:23:32]

What do you think of just iterating over all HTML attributes and exposing
everything with an aria- prefix? That would match what Firefox does.

I guess we'd have to exclude a few like aria-live that we're already handling,
above.

[je_julie(Not used), 2015/06/10 02:16:31]

When I looking into the inspection result from Accessibility Viewer,
Firefox has some html attributes depending on html tag for IAccessible2->Object
Attributes and all aria-attributes for ARIA->Attributes.('->' means inspection
menu depth.)
Chrome also has some html attributes for IAccessible2->Object Attributes and all
aria-attributes for ARIA->Attributes.

Because this part is for handling of IAccessible2->Object Attributes, I think we
don't need to expose all aria-attributes here.
I think it's enough to handle some html attribute according to spec. WDYT?

+  base::string16 dropEffect;
+  if (GetHtmlAttribute("aria-dropeffect", &dropEffect))
+    win_attributes_->ia2_attributes.push_back(L"dropeffect:" + dropEffect);
+
+  // Expose grabbed attribute.
+  base::string16 grabbed;
+  if (GetHtmlAttribute("aria-grabbed", &grabbed))
+    win_attributes_->ia2_attributes.push_back(L"grabbed:" + grabbed);
+
+  // Expose datetime attribute.
+  base::string16 datetime;
+  if (GetRole() == ui::AX_ROLE_TIME &&
+      GetHtmlAttribute("datetime", &datetime))
+    win_attributes_->ia2_attributes.push_back(L"datetime:" + datetime);
+
+  // Expose input-text type attribute.
+  base::string16 type;
+  if (GetRole() == ui::AX_ROLE_TEXT_FIELD &&
+      GetHtmlAttribute("type", &type))
+    win_attributes_->ia2_attributes.push_back(L"text-input-type:" + type);
+
   // If this is a web area for a presentational iframe, give it a role of
   // something other than DOCUMENT so that the fact that it's a separate doc
   // is not exposed to AT.
@@ -4285,6 +4302,7 @@ void BrowserAccessibilityWin::InitRoleAndState() {
       ia2_state |= IA2_STATE_SELECTABLE_TEXT;
       break;
     case ui::AX_ROLE_TIME:
+      role_name = html_tag;
       ia_role = ROLE_SYSTEM_TEXT;
       ia2_role = IA2_ROLE_TEXT_FRAME;
       break;