New issue
Advanced search Search tips

Issue 811071 link

Starred by 9 users
Status: Duplicate
Merged: issue 811968
Owner: ----
Closed: Feb 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Content scripts are not injected / executed on the page

Project Member Reported by igrigo...@chromium.org, Feb 10 2018 
Chrome Version: 64.0.3282.140
OS: 10.13.3

What steps will reproduce the problem?
(1) Install https://github.com/igrigorik/videospeed (unpacked or from Chrome Store)
(2) Navigate to YouTube.com, script is not injected?

What is the expected result?
Script should run on the page. 

What happens instead?
Everything was working well until a few days ago, at which point I started seeing reports from folks that script is not being injected. Details: https://github.com/igrigorik/videospeed/issues/310. 

Nothing changed in the extension code and I don't see any errors anywhere that would point back at the extension. When I look at the Sources > Content Script tab, I don't see the extension in the list. Also, I don't think VS is the only affected extension.. all of my other extensions are also not executed?

To make things more interesting, other sites (e.g. vimeo.com) seem to be working a-OK, which hints to me that there is something localized to YouTube? Shot in the dark: SW-related?

Any ideas?

Comment 1 by igrigo...@google.com, Feb 14 2018 

As a heads up for others running into this problem, I've narrowed down this behavior on my own machine due to new (corp) extension policy [1]. 

- chrome://policy
- Under ExtensionSettings > show value
-- "runtime_blocked_hosts" contains list of origins on which extensions (e.g. content scripts) may be blocked

In this case my machine has a new active policy that included youtube.com as a blocked host. Hence videospeed is not executed.

[1] https://support.google.com/chrome/a/answer/7517624?hl=en&ref_topic=7517516

---

The meta issue here is that when such a policy is active there is *no* developer or user feedback that content scripts specified via manifest are blocked from executing. At a minimum, there should be a developer warning (e.g. a console message) indicating as much, and ideally some user visible UI indicator that extension has been disabled.

Comment 2 by nrpeter@chromium.org, Feb 15 2018

Mergedinto: 811968
Status: Duplicate (was: Untriaged)
Thanks for the feedback, we're tracking improvements in crbug.com/811968
►

Sign in to add a comment