Bug 151583
| Summary: | Web Inspector: resolved breakpoints show as unresolved after navigating backwards | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Blaze Burg <bburg> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | graouts, inspector-bugzilla-changes, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | 151581 | ||
| Bug Blocks: | |||
Blaze Burg
STEPS TO REPRODUCE:
1. Set some breakpoints on a somewhat unique resource, like the main HTML page.
2. Navigate to an unrelated website.
3. Click the browser "back" button
4. You should immediately hit the breakpoint
ACTUAL:
The breakpoint is shown as dark gray (enabled but unresolved).
EXPECTED:
It should be dark blue (enabled and resolved).
Notes:
This seems masked prior to fix for the blocking bug 151581; in that case, breakpoints might not be saved on pagehide, so there's nothing to save the new breakpoints as we navigate away.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/23653306>