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

Issue 828261 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
█ lushnikov@chromium.org
dgozman@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac , Fuchsia
Pri: 2
Type: Bug



Sign in to add a comment

[DevTools] source window fragment / hash is missing from DevTools window title

Reported by zac.spit...@gmail.com, Apr 3 2018 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3386.0 Safari/537.36

Steps to reproduce the problem:
1. Open a SPA, i.e gmail, which uses the window.location.hash to identify the current page state
2. Open DevTools
3. Devtools title is missing the hash

What is the expected behavior?
fragments are important to identify which window/tab a DevTools instance refers to, they should be included

What went wrong?
window.location.pathname and window.location.search are included, but window.location.hash isn't

Did this work before? No 

Chrome version: 67.0.3386.0  Channel: canary
OS Version: 10.0
Flash Version:

Comment 1 by woxxom@gmail.com, Apr 3 2018 

As per git blame of devtools source suspecting 20f53c9672952cdd8e4d59c025ee11caaa7d28ff
"DevTools: Strip fragment from all urls passed to front-end by Page and Resource agents."
Landed in 29.0.1539.0

Comment 2 by krajshree@chromium.org, Apr 3 2018

Labels: Needs-Triage-M67

Comment 3 by elawrence@chromium.org, Apr 3 2018

Labels: FoundIn-67 FoundIn-65 OS-Chrome OS-Fuchsia OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Summary: [DevTools] source window fragment / hash is missing from DevTools window title (was: [DevTools] source window fragment / hash is missing from DevTools window title)
The CL in #1 definitely looks like the root cause.

Comment 4 by l...@chromium.org, Apr 3 2018

Cc: dgozman@chromium.org lushnikov@chromium.org
Status: WontFix (was: Untriaged)
Thanks for the report.  Given how much of our bindings rely on having no fragments and our current priorities, it is unlikely for us to move fragment-stripping deeper into DevTools anytime soon.  Closing for now, unless others have ideas.
►

Sign in to add a comment