<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.webkit.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4.1"
          urlbase="https://bugs.webkit.org/"
          
          maintainer="admin@webkit.org"
>

    <bug>
          <bug_id>195357</bug_id>
          
          <creation_ts>2019-03-05 22:00:14 -0800</creation_ts>
          <short_desc>Web Inspector: CPU Usage Timeline - don&apos;t eagerly render the Statistics and Sources sections</short_desc>
          <delta_ts>2019-03-05 22:00:14 -0800</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>WebKit</product>
          <component>Web Inspector</component>
          <version>WebKit Nightly Build</version>
          <rep_platform>All</rep_platform>
          <op_sys>All</op_sys>
          <bug_status>NEW</bug_status>
          <resolution></resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>Normal</bug_severity>
          <target_milestone>---</target_milestone>
          <dependson>195202</dependson>
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Devin Rousso">hi</reporter>
          <assigned_to name="Nobody">webkit-unassigned</assigned_to>
          <cc>inspector-bugzilla-changes</cc>
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>1512998</commentid>
    <comment_count>0</comment_count>
    <who name="Devin Rousso">hi</who>
    <bug_when>2019-03-05 22:00:14 -0800</bug_when>
    <thetext>Rather than specifically update the DOM of the Statistics and Sources sections whenever adding/removing a filter, we could create a new `WI.CPUTimelineStatisticsView` that has it&apos;s own `layout()` which we can then call `needsLayout` on so only it will re`layout` when adding/removing filters.  This would help reduce the overall size of CPUTimelineView.js and perhaps make some of the logic a bit more &quot;chunk&quot;able.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>