From chat w/ Devlin:

https://cs.chromium.org/chromium/src/chrome/browser/extensions/error_console/error_console.cc?q=error_console.cc&sq=package:chromium&g=0&l=177-187

it only respects the FeatureSwitch value if it has an override

so by default, we'll only look at which channel - and it's restricted to dev

we should just clean that whole method up to return the value of profile_->GetPrefs()->GetBoolean(prefs::kExtensionsUIDeveloperMode))

@James, Devlin: Any thoughts on this? Should we come up with a fix and merge to M68, or at this point better to wait for 69?

Markning this as Available, since @hcarmona was able to reproduce.

Hmm... with where we are in the release cycle, I don't see a strong reason to push for a merge to 68.  I'm fine fixing for 69 and launching then.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/3e3ae8fcb55c804981fd83075cffda76f3d57339

commit 3e3ae8fcb55c804981fd83075cffda76f3d57339
Author: Esmael El-Moslimany <aee@chromium.org>
Date: Thu Jul 19 03:45:11 2018

Extensions: make error console enabled if profile is in dev mode

Bug:  863145 
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: Ia8b82930d525b9ba3eee1e3332da1d5e35809131
Reviewed-on: https://chromium-review.googlesource.com/1141220
Commit-Queue: Esmael El-Moslimany <aee@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#576356}
[modify] https://crrev.com/3e3ae8fcb55c804981fd83075cffda76f3d57339/chrome/browser/extensions/error_console/error_console.cc
[modify] https://crrev.com/3e3ae8fcb55c804981fd83075cffda76f3d57339/chrome/browser/extensions/error_console/error_console_unittest.cc
[modify] https://crrev.com/3e3ae8fcb55c804981fd83075cffda76f3d57339/chrome/browser/resources/md_extensions/error_page.js
[modify] https://crrev.com/3e3ae8fcb55c804981fd83075cffda76f3d57339/chrome/browser/resources/md_extensions/manager.html