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

Issue 887187 link

Starred by 1 user
Status: Unconfirmed
Owner: ----
Cc:
█ krajshree@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chrome extension can not inject the script file to new blank tab. (new version)

Reported by tran.ngo...@gmail.com, Sep 20 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36

Steps to reproduce the problem:
1. Install my extension
2. Click any area in new blank tab.
3. All function in my javascript at extension not working.

What is the expected behavior?
In the blank tab the function working as other tab(having url)

What went wrong?
My script from extension not inject into new blank tab. So my feature not working at blank tab.

Did this work before? Yes Chrome v.62

Does this work in other browsers? N/A

Chrome version: 69.0.3497.100  Channel: n/a
OS Version: 10.0
Flash Version: 

I have been created the chrome extension and it working fine. But 
currently, after the chrome update to new version (v. 69.0.3497.100 ) it 
not work at blank tab. I found down my script in extension 
(monitorEvent.js) not inject in to chrome when i open new blank tab. Is 
chrome prevent the script inject to browser when i open new blank tab? or i 
missing something? I have researched too much but not find to solution. 
Please help me solved this problem.
manifest.png
19.2 KB View Download

Comment 1 by woxxom@gmail.com, Sep 20 

See https://crrev.com/2978953002/

On 2017/07/22 14:27:54, wOxxOm wrote:
> Why the sudden change after many years of allowing content scripts in the iframe
> of NTP? Wouldn't users of the extensions that allowed customizing/restyling the
> standard NTP feel confounded and annoyed? It'd be nice if you post a publicly
> accessible issue or an announcement explaining the change so that the extension
> developers and users know it's not a bug.

Hey wOxxOm!  There's a few reasons for this change.  One is to enforce policy,
the other is for consistency.

We've had a public policy [1] for awhile now that states that modification of
the NTP through anything other than Chrome URL overrides isn't allowed (though
we didn't begin enforcing this policy in many cases until July 1st).  This is
merely bringing chrome code more inline with that same policy to help prevent
surprise if an extension is modifying the NTP and is taken down for policy
violations.

This is also for consistency, since we've actually treated scripts on the NTP
differently for years now, due to certain NTP magic.  For example, the URL seen
by the browser on the NTP is chrome://newtab, but the url in the renderer is
https://www.google.com/_/chrome/newtab.  Since chrome.tabs.executeScript checks
the URL in the browser, the script would be denied, even though content scripts
(checked in the renderer) would be allowed.  In theory, these permissions should
*not* be different.  Similarly odd, if the user is using the local ntp
(chrome-search://local-ntp/local-ntp.html), injection would already be
disallowed in both the renderer and the browser.  And, if we go waaaaay back,
the NTP used to be pure WebUI with an URL of chrome://newtab, where injections
were again disallowed.  Rather than have inconsistent behavior depending on the
type of script injection the extension uses, we want to have consistency
throughout the system.

[1] https://developer.chrome.com/webstore/program_policies#extensions

Comment 2 by vamshi.kommuri@chromium.org, Sep 20

Labels: Needs-Bisect Needs-Triage-M69

Comment 3 Deleted

Comment 4 by tran.ngo...@gmail.com, Sep 20 

Hi @Vamshi.kommuri

As your comment, currently the new chrome(v.69) don't have inject the script when i open new blank tab. right? or have any config for solved this case.

Comment 5 by krajshree@chromium.org, Sep 20

Cc: krajshree@chromium.org
Components: Platform>Extensions
Labels: Triaged-ET Needs-Feedback
reporter@ - Thanks for filing the issue...!!
Could you please provide a sample extension file/url to test the issue from TE-end. Also please provide manual reproducible steps and a screen cast for better understanding of the issue. This will help us in triaging the issue further.

Thanks...!!
►

Sign in to add a comment