MD Settings: Allow search within settings to track multiple requests separately.

chrome/test/data/webui/settings/cr_settings_browsertest.js

Index: chrome/test/data/webui/settings/cr_settings_browsertest.js
diff --git a/chrome/test/data/webui/settings/cr_settings_browsertest.js b/chrome/test/data/webui/settings/cr_settings_browsertest.js
index 565e21258953a40bc45e1a3645357c7627595aaf..6d4a2cf582876b056789a248026635dbf63f2c87 100644
--- a/chrome/test/data/webui/settings/cr_settings_browsertest.js
+++ b/chrome/test/data/webui/settings/cr_settings_browsertest.js
@@ -1204,6 +1204,9 @@ CrSettingsSearchTest.prototype = {
   browsePreload: 'chrome://md-settings/settings_page/settings_section.html',
 
   /** @override */
+  runAccessibilityChecks: false,

[Dan Beam, 2017/03/14 00:44:28]

i don't think we want this.  i think we want to change a specific test or just
not make a11y tests errors

[dpapad, 2017/03/14 03:28:11]

Reverted.
The way we test accessibility is weird. We test whatever is left in the DOM
after our actual test finishes. Most importantly it causes confusion when a test
fails, because when it fails different things are left in the DOM, and then
additional accessibility errors are showing, which are unrelated to the original
failure.

My thinking is that we should disable accessibility checks for all our unit
tests, and add a single test that intentionally force renders everything in the
DOM and just does a11y checks.

+
+  /** @override */
   extraLibraries: CrSettingsBrowserTest.prototype.extraLibraries.concat([
     'search_settings_test.js',
   ]),