Commit 6eb58b98 authored by Dominic Mazzoni's avatar Dominic Mazzoni Committed by Commit Bot

Enable the AccessibilityExposeHTMLElement flag on trunk.

Fix one remaining tiny test failure, all others should now be fixed.
We should leave this flag around for at least one milestone just in
case, but if there are no issues then we can remove the flag and
hard-code it this way.

This is a big step towards getting rid of the "ignored and not
included in the tree" state.

Bug: 1063155
Change-Id: I92241af7ec752dc537919740ef96c7e149d460e5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2448656Reviewed-by: default avatarAaron Leventhal <aleventhal@chromium.org>
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#813794}
parent 4d1156e0
......@@ -186,7 +186,7 @@ IN_PROC_BROWSER_TEST_F(AccessibilityIpcErrorBrowserTest,
bad_accessibility_event.updates[0].root_id = 1;
bad_accessibility_event.updates[0].nodes.resize(1);
bad_accessibility_event.updates[0].nodes[0].id = 1;
bad_accessibility_event.updates[0].nodes[0].child_ids.push_back(2);
bad_accessibility_event.updates[0].nodes[0].child_ids.push_back(999);
for (int iteration = 0; iteration < max_iterations; iteration++) {
// Make sure the manager has been created.
......
......@@ -21,7 +21,7 @@ bool IsAccessibilityExposeDisplayNoneEnabled() {
// Enable exposing the <html> element to the browser process AXTree
// (as an ignored node).
const base::Feature kEnableAccessibilityExposeHTMLElement{
"AccessibilityExposeHTMLElement", base::FEATURE_DISABLED_BY_DEFAULT};
"AccessibilityExposeHTMLElement", base::FEATURE_ENABLED_BY_DEFAULT};
bool IsAccessibilityExposeHTMLElementEnabled() {
return base::FeatureList::IsEnabled(
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment