[Webkit-unassigned] [Bug 104780] New: Web Inspector: Crash in InspectorDOMAgent::pushNodePathToFrontend when inspecting document with CSS generated content

[bugzilla-daemon at webkit.org]

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

           Summary: Web Inspector: Crash in
                    InspectorDOMAgent::pushNodePathToFrontend when
                    inspecting document with CSS generated content
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Web Inspector
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: graouts at apple.com
                CC: timothy at apple.com, keishi at webkit.org,
                    pmuellr at yahoo.com, joepeck at webkit.org,
                    pfeldman at chromium.org, yurys at chromium.org,
                    apavlov at chromium.org, loislo at chromium.org,
                    vsevik at chromium.org,
                    webkit-bug-importer at group.apple.com,
                    web-inspector-bugs at googlegroups.com


When using the LayerTreeAgent to inspect the layer tree of a page containing CSS generated content, we hit the first ASSERT in InspectorDOMAgent::pushNodePathToFrontend due to the node being 0 as passed from InspectorDOMAgent::pushNodePathForRenderLayerToFrontend. Indeed, that method naively expects all RenderLayers to be associated with a Node, except there may be layers generated by CSS generated content. We should make that method more robust so that it checks for an associated Node for the provided RenderLayer and returns 0 in case there is no such node before calling into InspectorDOMAgent::pushNodePathToFrontend.

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