New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 693788 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Out until 24 Jan
Closed: Feb 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 3
Type: Bug
Team-Security-UX



Sign in to add a comment

Extension content script doesn't run on origins with JS disabled

Project Member Reported by lgar...@chromium.org, Feb 17 2017

Issue description

Chrome 58.0.3013.3
OSX 10.12.3

What steps will reproduce the problem?
(1) Disable JS for HTTP pages.
(2) Install https://chrome.google.com/webstore/detail/ugly-http/mlneofdamjbcmahdcjjbmbjomedanhal
(3) Visit an HTTP page

What is the expected result?
The extension runs a content script that adds a `ugly-http-status-loaded` class to the body [1].

What happens instead?
The page stays at 10% opacity, which indicates that the content script did not run [2].
In addition, pressing the extension button also doesn't do anything.

nasko@, I'm filing this at your suggestion [3].
Could you help pass this on for triage? :-)

[1] https://github.com/lgarron/ugly-http-extension/blob/d17cd20a57af27c627472f081313a60651530255/content.js#L31
[2] https://github.com/lgarron/ugly-http-extension/blob/d17cd20a57af27c627472f081313a60651530255/ugly.css#L1
[3] https://twitter.com/nasko/status/829494417287360512
 
Status: WontFix (was: Assigned)
Actually, I think I finally figured it out. The `setTimeout` never fires. This can technically happen on any page, but in practice it was only happening on pages with JS disabled.

Sign in to add a comment