Bug 157186 - Web Inspector: the console should coalesce more rendering when adding messages that were logged before the Inspector was open
Summary: Web Inspector: the console should coalesce more rendering when adding message...
Status: RESOLVED DUPLICATE of bug 155629
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: WebKit Nightly Build
Hardware: All All
: P2 Normal
Assignee: Nikita Vasilyev
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2016-04-29 10:01 PDT by BJ Burg
Modified: 2016-05-02 11:48 PDT (History)
7 users (show)

See Also:

Attachments
[HTML] Reduction (395 bytes, text/html)
2016-05-02 11:44 PDT, Nikita Vasilyev 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description BJ Burg 2016-04-29 10:01:32 PDT 
If there are 100 warnings, you have to sit there and wait for all of them to render and scroll up. This bogs down processing of the initial surge in events when the inspector opens, and makes it feel unresponsive at first.


If possible we should avoid doing sync layout work when handling messages in the initial few seconds, especially if it's redundant. We should batch the rendering using requestAnimationFrame and/or sending them over protocol from the backend.
Comment 1 Radar WebKit Bug Importer 2016-04-29 10:04:12 PDT 
<rdar://problem/26006165>
Comment 2 Nikita Vasilyev 2016-04-29 10:41:46 PDT 
This is going to be mitigated by bug 155629
"Web Inspector: Adding a new console message shouldn't modify DOM when the console log is hidden".

Besides, I'm going to use requestAnimationFrame batching.
Comment 3 Nikita Vasilyev 2016-05-02 11:44:39 PDT 
Created attachment 277916 [details]
[HTML] Reduction
Comment 4 Nikita Vasilyev 2016-05-02 11:48:38 PDT 
The attached reduction works pretty smooth.

I believe all the mentioned issues were addressed in bug 155629.
If it isn't the case, feel free to reopen this bug.

*** This bug has been marked as a duplicate of bug 155629 ***