New issue
Advanced search Search tips

Issue 811063 link

Starred by 5 users

Issue metadata

Status: Archived
Owner: ----
Closed: Apr 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

chrome.webRequest.onBeforeRequest regression on chrome 64 mac.

Reported by gaetan.h...@gmail.com, Feb 10 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36

Steps to reproduce the problem:
1. Create an extension that add a listener with chrome.webRequest.onBeforeRequest.addListener:
chrome.webRequest.onBeforeRequest.addListener(console.log, {urls: ["<all_urls>"], types:["main_frame"]},["blocking"])

2. declare <any_url> permission in manifest.json
3. load the extension
4. navigate to any url from the address bar.
5. notice the callback onBeforeRequest is not called.

What is the expected behavior?
The callback should be called when navigating to any url and the request should be logged in the background extension console.

What went wrong?
In chrome 63 on mac, this worked perfectly and the callback was properly called. 
This is also working as expected on chrome window 64 so it looks like it's only a regression on chrome mac. I haven't tested on chrome linux.

Did this work before? Yes 63

Does this work in other browsers? Yes

Chrome version: 64.0.3282.140  Channel: stable
OS Version: OS X 10.13.3
Flash Version: Shockwave Flash 28.0 r0
 
Components: Platform>Extensions>API Internals>Network
I do not know how prioritization is managed (if at all), but do you happen to perhaps have another installed extension that uses the web request API? If so, perhaps your extension is not "winning" the race or something.
You were right, that is the case. I have a mandatory extension from my company that must catch them before. 
Although this use to work no problem in chrome  63, so something clearly changed in 64.
I just tested in chrome 64 on my wife (non-corp) laptop and it does not have that issue because there are no competing extension.
Labels: Needs-Triage-M64 Needs-Bisect
Labels: Triaged-ET Needs-Feedback
Thanks for filing the issue!

@Reporter: Could you please share a sample test file/extension which helps to triage the issue in a better way from ET end.

Thanks!

Comment 6 by rch@chromium.org, Feb 21 2018

@reporter: Can you provide the requested information? Otherwise we'll need to close this bug.
Components: -Internals>Network
Removing Internals>Network, this seems like an extensions issue to me. I don't think the net team has enough expertise to debug this.
Project Member

Comment 8 by sheriffbot@chromium.org, Apr 5 2018

Status: Archived (was: Unconfirmed)
No feedback was received in the last 30 days from the reporter, so archiving this issue. Please re-open or file a new bug if necessary.

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

Sign in to add a comment