I don't believe it's accurate to say it's "accessible by any user", the net effect of the policy will be (over a time span of months or years) to limit ad blocking only to the most technically capable users who understand how to do what you describe.

Moreover, extensions that continue to use this behavior are required to adhere to manifest v2, and support for that manifest will likely eventually be deprecated. Chrome blocked the store from serving and updating manifest v1 extensions after a deprecation period.

Google rapidly deprecated version 1, from Chrome 18's release adding version 2 in March 2012 to blocking updating in March 2013, to removal of all extensions that had not updated from the Chrome Web Store in September 2013.

If Manifest v3 follows a similar trajectory, Chrome is on a path to remove uBlock Origin from its web store in 2 years.

Just to clarify, what I am referring to is the claim that it’s limited to paying enterprise customers. I could be wrong but I believe that the enterprise policy bits are what matter, and as far as I know all of those are available in Chrome/Chromium today, via group policy systems. When I say “accessible” I am specifically referring to that bit, definitely not suggesting ordinary users should do that.

One of my favorite things with Firefox is the ability to “edit and resend” requests in the browser devtools. I’m sure there are plugins that do something similar on chrome/chromium. But I use it all the time and my colleagues are always blown away when I show them this.

Whoa, never knew that was a thing. I found FF's dev tools quite bulky and clunky in the past, but I might have to give it another go.

That's the only reason I keep falling back to Chrome, the dev tools are just so much more refined.

The one thing I always liked about Chrome dev tools was the ability to introspect WebSocket frames. Last I checked this couldn’t be done in Firefox :(

Otherwise, I have found Firefox dev tools to be fairly competitive. I liked the CSS Grid stuff they had around the launch of Quantum; it made it easier for me to jump into Grid.

I use Firefox personally, but develop with Chrome. I have a hard time getting stack traces from Firefox reliably. Oftentimes one of the following occurs on Firefox:

There is no error, but the page won't load. There is an error, but the error message is generic. There is an error message, but no stack trace.

When I switch to chrome, I always get the error and stack trace without any further code modifications.

I make sure to clean up for Firefox in releases. But it's just impossible to develop without error messages and traces. I'm on Ubuntu using the latest stable releases.

Ugh. Is this really still broken? I'm not a web dev but I remember having to switch to Chromium 6-8 months ago when I needed to debug a websockets issue.

Chromium and Opera have the same dev tools and doesn't tie you to chrome.

Ah yeah, on occasion I will boot Firefox at work for this capability.

Truth be told I know of nothing similar in Chrome/Chromium, but you can do something similar using the healthy number of “Copy Request As” context options. I like to copy as fetch and manipulate it in the console. It’s not perfect but it’s useful.

Is it this?

https://cloud.google.com/chrome-enterprise/browser/download

Key point (for Windows) on that page is:

  ADM/ADMX templates with 300+ user and device policies

ADM/ADMXs are a list of settable policies (rules) that Chrome will read from the Windows Registry on startup[1]. I'm going to make a huge assumption that the Chrome.exe for Enterprise users is no different to the Chrome.exe that everyone else uses, and it switches into 'Enterprise' mode if it sees certain key policy entries in the Registry[2].

These polices are typically set on a Windows Domain Controller and are pushed to Domain member machines (and users) on the network on a regular basis.

However end-users can simulate the policies by setting these Registry entries manually (There are about 4 places in the Registry where they live). Depending on where Chrome looks, the user may need local admin privileges to do this.

So, what we really need is a 'Chrome Enterprise Enabler' tool, that does this automatically for non-technical users. They would run this tool, the required Registry keys would be enabled, and WebRequest API based Ad-blocking would continue to work.

Unfortunately, none of this helps Linux users as I don't see a Linux Enterprise Chrome package.

---

[1] I've got 25+ years of Windows domain administration under my belt, this stuff used to be my bread-and-butter.

[2] Even if not, extracting just the Chrome MSI installer from the Enterprise bundle is trivial.

Chrome MSI and chrome EXE installers work a little differently. The MSI installer by default installs to the program files directory. I've seen the EXE installer often installed to the local user profile. to convert a regular install to Enterprise you would probably have to uninstall the local version and then install the MSI.

ADM templates are something Firefox is sorely lacking at the moment. I remember reading that it is on the road map but that does not help out much. Nevertheless, I installed both chrome and Firefox and my organization. I like Firefox and use it myself, but sadly it's just not as easy to administer as chrome.

So two things. The MSI installer will convert a local (EXE) installation to a global install (updating shortcuts and removing the local profile install whilst preserving the chrome profile).

Second, Firefox does have ADMX policies (ADMX being used primarily after Vista): https://github.com/mozilla/policy-templates. I believe it took them so long because they were initially reluctant, user freedom etc. But I guess Chrome's success in enterprise made them reconsider. Honestly I never considered Firefox for our Windows Domain because of the lack of Group Policy support. Now I deploy both and users have options :)

FWIW it Is supported under Linux I believe, but unfortunately the documentation is lacking. If I recall correctly, you have to drop JSON files in the right places.

These are just features and settings, there's no requirement to use them.

The main point isn't listed on the page.

The Enterprise installer installs Chrome to the operating system.

Regular chrome installs in your user profile.

> These are just features and settings, there's no requirement to use them.

I think you missed my point. Google say that the Enterprise version will continue to support WebRequest API. If the Enterprise version is the same codebase as the normal version, then it's a good educated guess that the Policy keys are whats controlling that.

Looks like some useful stuff for deploying to Enterprise, but actually as far as I know the enterprise functionality exists in normal installations. Like for example, this stuff:

http://dev.chromium.org/administrators/policy-list-3

To be honest, I am not the most knowledgeable here; I just know I used the enterprise policy system on my personal laptop without issue.

See my sibling comment.

What platform are you on? I tried Firefox quantum yesterday and could not stand the text rendering. Gmail looks awful. But I don't have a 4k monitor yet...