Open Bug 482925 Opened 15 years ago Updated 2 years ago

[HTML5] Tweak HTML5 tree builder flushes for better perceived responsiveness

Categories

(Core :: DOM: HTML Parser, defect, P4)

Other Branch
defect

Tracking

()

People

(Reporter: hsivonen, Unassigned)

References

Details

Should tweak HTML5 tree builder flush timing so that the perceived responsiveness is better.
Priority: -- → P3
There are two issues:
 1) Tuning how tree ops are flushed when not speculating (TODO fallout from bug 502568).
 2) Making tree op flushes that don't need to run to completion synchronously (i.e. non-document.write/close flushes) regulate the maximum number of tree ops in one flush and scheduling a continuation flush if the initial queue is too long.
Depends on: 502568
Note to self: Don't defer flushing before </head> has been flushed.
Not Firefox 4 material.
Priority: P3 → P4
Less important in the multi-process world. Doing anything informed here would need a good benchmarking setup.
Assignee: hsivonen → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.