WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
NEW
124685
Web Inspector: assertion when reloading page after selecting resource
https://bugs.webkit.org/show_bug.cgi?id=124685
Summary
Web Inspector: assertion when reloading page after selecting resource
Brian Burg
Reported
2013-11-20 15:53:30 PST
Stack trace attached (can't copy it out of console.. :() Steps to reproduce: 1. Open a single frame webpage 2. Open web inspector 3. Select any resource in the resources sidebar panel, or switch away from the DOM tree content view. 4. Reload the page This doesn't happen if reloading when the main frame resource's DOM tree content view is displayed, or if selecting a resource and navigating to a different page. I think there is something causing the same content view to be entered into the backForwardList twice, or more than one content view thinks it is displayed at the same time. A brute force fix is to simply hide all visible content views before disassociating from them (rather than only hiding the content view associated with the 'current' history entry), but this feels like ignoring the root cause.
Attachments
stack trace from 2nd level inspector
(36.07 KB, image/png)
2013-11-20 15:54 PST
,
Brian Burg
no flags
Details
View All
Add attachment
proposed patch, testcase, etc.
Brian Burg
Comment 1
2013-11-20 15:54:01 PST
Created
attachment 217489
[details]
stack trace from 2nd level inspector
Brian Burg
Comment 2
2013-11-20 16:23:24 PST
This seems related to the fact that there are nested content view containers and histories. However it's not clear why one list has two visible entries, as the nested histories don't touch each other.
Antoine Quint
Comment 3
2013-11-21 01:47:32 PST
(In reply to
comment #0
)
> Stack trace attached (can't copy it out of console.. :()
Hmm, this should work by either selecting the row and Cmd+C or drag to select the text.
Radar WebKit Bug Importer
Comment 4
2014-02-14 09:52:24 PST
<
rdar://problem/16070881
>
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug