[Webkit-unassigned] [Bug 53657] New: Web Inspector: Show parser line/col with paint events on timeline

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Feb 2 20:37:25 PST 2011


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

           Summary: Web Inspector: Show parser line/col with paint events
                    on timeline
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Enhancement
          Priority: P2
         Component: Web Inspector
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: tonyg at chromium.org
                CC: timothy at apple.com, rik at webkit.org, keishi at webkit.org,
                    pmuellr at yahoo.com, joepeck at webkit.org,
                    pfeldman at chromium.org, yurys at chromium.org,
                    bweinstein at apple.com, apavlov at chromium.org,
                    jamesr at chromium.org, loislo at chromium.org,
                    tonyg at chromium.org


The inspector timeline shows paint events along with some useful details like the size and location. It would be really useful to me if it also showed the current line/column position of the parser if the document has an active parser.

More details:
James and I were troubleshooting an interesting performance problem where the first paint time of a page appeared to move way back. We had a suspicion that different amounts of content were being painted in the first paint, but were unable to confirm with the inspector alone. We ended up hacking printfs into RenderFrame which just printed out document->parser()->asScriptableParser()->m_line and m_column. That extra bit of information was able to confirm that the change had in fact improved the time when the same content got painted, but dropped an earlier paint. Hopefully we can get that info in the inspector in the future.

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



More information about the webkit-unassigned mailing list