WebUI: Fix/suppress some existing violations of no-restricted-globals.

chrome/browser/resources/chromeos/chromevox/.eslintrc.js

Index: chrome/browser/resources/chromeos/chromevox/.eslintrc.js
diff --git a/chrome/browser/resources/chromeos/chromevox/.eslintrc.js b/chrome/browser/resources/chromeos/chromevox/.eslintrc.js
new file mode 100644
index 0000000000000000000000000000000000000000..06b7bfc89be54c37d61aefac9956799202241c2c
--- /dev/null
+++ b/chrome/browser/resources/chromeos/chromevox/.eslintrc.js
@@ -0,0 +1,15 @@
+// Copyright 2017 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+module.exports = {
+  'env': {
+    'browser': true,
+    'es6': true
+  },
+  'rules': {
+    // Override restrictions for document.getElementById usage since,
+    // chrome://resources/js/util.js is not accessible for chromevox.
+    'no-restricted-properties': 'off',

[Dan Beam, 2017/06/05 19:04:01]

what if we write other checked based on no-restricted properties in the future
other than getElementById vs $?

[dpapad, 2017/06/05 19:11:58]

It would be disabled also. The granularity we have from within this config file
is at the rule level. A rule can be turned on/off as a whole.

[Dan Beam, 2017/06/05 19:23:10]

i was mainly asking to see if we have a plan.

there's 51 of occurrences of `document.getElementById` in
chrome/browser/resources/chromeos/*vox so that's probably not work individually
disabling.

[dpapad, 2017/06/05 19:32:40]

Yes, already checked number of occurrences before deciding to go with the config
file approach. I don't have a great plan for this yet. Issue
https://github.com/eslint/eslint/issues/7957 seems related. Eventually I think
we need help from ESLint to address this problem, by being able to override
sub-rule properties, instead of turning off the entire rule. I'll ask on their
tracker for this.

+  },
+};