New issue
Advanced search Search tips

Issue 745764 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Jul 19
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Connection between WebRequest and Debugger

Reported by oliver.h...@gmail.com, Jul 18 2017

Issue description

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

Steps to reproduce the problem:
I build a extension which uses WebRequest-API and Debugger. I want to connect the Request Data from both APIs, but the frameId / requestId doesn't match.

At WebRequest the requestId is a string with format "01234". At Debugger the requestId is a string with the format "54321.123".

Nearly the same issue exists with the frameId. At WebRequest the frameId is a number with format 1234. At Debugger the frameId is a string with the format "54321.123".

How can these data matched? What is the best way?

What is the expected behavior?

What went wrong?
Type doesn't match.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 59.0.3071.115  Channel: stable
OS Version: 10.0
Flash Version:
 
Labels: Needs-Triage-M59
Components: Platform>Extensions
Labels: TE-NeedsTriageHelp
Requesting someone from extension team to look in to this issue.

Thanks!
Project Member

Comment 4 by sheriffbot@chromium.org, Jul 19

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

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

Sign in to add a comment