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

Issue 785103 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 9
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

extension's content script(run_at:document_idle) failed to inject to page

Reported by liangran...@gmail.com, Nov 15 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36

Steps to reproduce the problem:
1. OS: Windows Server 2008 RC2
2. Chrome: 62.0.3202.94 (Official Build) (64-bit) (cohort: 62_94_win)
3. Extension Content Script
> "run_at": "document_idle",
> "matches": ["http://*/*", "https://*/*"],
4. Page Link: http://news.sina.com.cn/c/2017-11-13/doc-ifynrsrf4477546.shtml
5. DevTools Sources Panel
> NO Content scripts.
NOTE: if you set "run_at": "document_start", window.onload or "DOMContentLoaded" callback in content_script will not be invoked.

What is the expected behavior?

What went wrong?
content script(run_at:document_idle) failed to inject to page

WebStore page: 

Did this work before? N/A 

Chrome version: 62.0.3202.94  Channel: stable
OS Version: 6.1
Flash Version: 27.0.0.187
 
Labels: Needs-Triage-M62
Cc: krajshree@chromium.org
Labels: Triaged-ET Needs-Feedback
liangran10000@ - Thanks for filing the issue...!!

Could you please provide a sample extension to test the issue from TE-end.
A screen cast or screenshot explaining the exact issue will be more helpful.
This will help us in triaging the issue further.

Thanks...!! 

Comment 3 Deleted

Project Member

Comment 4 by sheriffbot@chromium.org, Nov 20 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 Deleted

Comment 6 Deleted

Cc: kebalaji@chromium.org
Labels: Needs-Feedback
@Reporter: Could you please attach a sample testcase file to test the issue.

Thanks!
I attached a sample extenstion, but the comment's status is deleted.
Any extension on this page (Page Link: http://news.sina.com.cn/c/2017-11-13/doc-ifynrsrf4477546.shtml) can test the issue.
Project Member

Comment 10 by sheriffbot@chromium.org, Dec 6 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "kebalaji@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback
@Reporter: Could you try to test this issue on latest chrome stable# 67.0.3396.62 and let us know if the issue still persists, if possible could you please provide screencast of the issue which help in better understanding. You can download chrome latest stable from URL: https://www.chromium.org/getting-involved/dev-channel.

Thanks!
Cc: vamshi.kommuri@chromium.org
Status: WontFix (was: Unconfirmed)
As there is no update from the reporter since a long time, marking this issue as WontFix.
Please feel free to raise a new bug if any issues are observed on the latest Chrome builds.

Thanks..

Sign in to add a comment