Fast path for HTML parser if document.write is disabled via feature policy |
||||||
Issue descriptionHTML 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.
,
Aug 16 2016
,
Aug 19 2016
,
Apr 29 2017
,
Apr 30 2018
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
,
May 7 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by kouhei@chromium.org
, Aug 16 2016