5

I am using an experimental feature in Chrome called "Request Blocking" to simulate the behavior of an ad blocker which is blocking our New Relic script.

After the feature is enabled:

New menu option to block the URL

and after refreshing:

chrome dev tools - resource blocked - yay!

but when I access the menu again, the only Request Blocking option is:

no unblock option

Obviously this feature is experimental and may be incomplete (maybe it's just not coded yet!). Has anyone uncovered a way to un-block resources when using the Request Blocking experimental feature?

I uncovered the feature from this SO post.

Solution: resetting the browser as the accepted answer suggests worked, but I was able to keep my settings and only "undo" the experiment's changes by disabling the experiment and restarting Chrome.

Community
  • 1
  • 1
pherris
  • 17,195
  • 8
  • 42
  • 58

1 Answers1

6

When in doubt, try resetting Chrome before using an experiment.

I was seeing similar problems when I first enabled the experiment, but after resetting Chrome, there's now a blue icon next to the Offline checkbox, and a Request Blocking tab in the Drawer. Clicking the blue icon opens the tab.

request blocking UI

Kayce Basques
  • 23,849
  • 11
  • 86
  • 120
  • 1
    Resetting Chrome worked but should be considered a nuclear option. I was able to disable the experiment, restart the browser and see that the request was no longer blocked. – pherris Jan 03 '17 at 14:56