[Webkit-unassigned] [Bug 122127] New: Web Inspector: changing cluster's content view causes strange navigation history

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=122127

           Summary: Web Inspector: changing cluster's content view causes
                    strange navigation history
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: Web Inspector
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: burg at cs.washington.edu
                CC: timothy at apple.com, joepeck at webkit.org,
                    webkit-bug-importer at group.apple.com, graouts at apple.com


There's a strange interaction between changing content views within a ClusterContentView and the top-level ContentBrowser's back/forward navigation buttons (goForward/goBack). 

Repro steps:
1. Start by showing a FrameContentView (click on main frame tree element)
2. Navigate to some other tree elements
3. Click the back button to go back to the FrameContentView
4. Change between DOM and Source view.
5. Click the forward button to see the inserted (instead of truncated + appended) new history entry.

This causes a back-forward entry to be added to a nested ContentViewContainer, but does not splice/prune forward entries from the top-level back forward list. So, there's a strange effect where you can extend the user-facing history (i.e., how many clicks needed to make ContentBrowser.{canGoBack, canGoForward} return false) from within.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.