New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 637874 link

Starred by 8 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature

Blocked on:
issue 623682



Sign in to add a comment

Fast path for HTML parser if document.write is disabled via feature policy

Project Member Reported by csharrison@chromium.org, Aug 15 2016

Issue description

HTML parser has a lot of overhead for speculative tokenizing. This is only necessary for document.write.

If document.write is disabled for the document, we can assume all tokens are correct, and we can stop sending / storing checkpoints all over the place in the parser code.

I may do some perf/memory testing on some big sites to see if this is a win. If so, this could be a nice carrot to encourage sites to use the feature policy here.
 

Comment 1 by kouhei@chromium.org, Aug 16 2016

sgtm

Blockedon: 623682

Comment 3 by tkent@chromium.org, Aug 19 2016

Status: Available (was: Untriaged)

Comment 4 Deleted

Labels: -Performance Performance-Loading
Project Member

Comment 6 by sheriffbot@chromium.org, Apr 30 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 7 by tkent@chromium.org, May 7 2018

Labels: -Hotlist-Recharge-Cold
Status: Available (was: Untriaged)

Sign in to add a comment