Bug 1452143: Don't test content CSS error reporting in the browser console. r=jryans

The browser console doesn't enable the cssErrorReportingEnabled bit on the
content process remote windows, and making it work seems non-trivial and kinda
useless per the firefox-dev@ discussions. So just remove this test.

MozReview-Commit-ID: GMGuQC7YNof

devtools/client/webconsole/test/mochitest/browser_console_error_source_click.js

@@ -9,19 +9,14 @@
 "use strict";
 
 const TEST_URI = "data:text/html;charset=utf8,<p>hello world" +
-                 "<button onclick='foobar.explode()' " +
-                 "style='test-color: green-please'>click!</button>";
+                 "<button onclick='foobar.explode()'>click!</button>";
 
 add_task(async function() {
   await addTab(TEST_URI);
+
   let hud = await HUDService.toggleBrowserConsole();
   ok(hud, "browser console opened");
 
-  // Enable CSS warnings and errors.
-  await setFilterState(hud, {
-    css: true
-  });
-
   // On e10s, the exception is triggered in child process
   // and is ignored by test harness
   if (!Services.appinfo.browserTabsRemoteAutostart) {
@@ -36,9 +31,6 @@ add_task(async function() {
 
   await waitForMessageAndViewSource(hud,
     "ReferenceError: foobar is not defined");
-  await waitForMessageAndViewSource(hud,
-    "Unknown property \u2018test-color\u2019.");
-  await resetFilters(hud);
 });
 
 async function waitForMessageAndViewSource(hud, message) {