Chromium Code Reviews| Index: Source/core/html/parser/HTMLParserScheduler.cpp |
| diff --git a/Source/core/html/parser/HTMLParserScheduler.cpp b/Source/core/html/parser/HTMLParserScheduler.cpp |
| index 7825c9c661cdaacfd0449fb19ad29b9980acc697..63426e606ff09536e18fa0aa485e58dafb3fb75e 100644 |
| --- a/Source/core/html/parser/HTMLParserScheduler.cpp |
| +++ b/Source/core/html/parser/HTMLParserScheduler.cpp |
| @@ -88,14 +88,6 @@ HTMLParserScheduler::~HTMLParserScheduler() |
| void HTMLParserScheduler::continueNextChunkTimerFired(Timer<HTMLParserScheduler>* timer) |
| { |
| ASSERT_UNUSED(timer, timer == &m_continueNextChunkTimer); |
| - // FIXME: The timer class should handle timer priorities instead of this code. |
| - // If a layout is scheduled, wait again to let the layout timer run first. |
| - // FIXME: We should fix this by reducing the max-parse-time instead of |
| - // artificially forcing the parser to yield agressively before first layout. |
| - if (m_parser->document()->shouldParserYieldAgressivelyBeforeScriptExecution()) { |
|
abarth-chromium
2014/03/29 20:20:35
Can we delete shouldParserYieldAgressivelyBeforeSc
|
| - m_continueNextChunkTimer.startOneShot(0, FROM_HERE); |
| - return; |
| - } |
| m_parser->resumeParsingAfterYield(); |
| } |
| @@ -115,7 +107,6 @@ void HTMLParserScheduler::scheduleForResume() |
| m_continueNextChunkTimer.startOneShot(0, FROM_HERE); |
| } |
| - |
| void HTMLParserScheduler::suspend() |
| { |
| ASSERT(!m_isSuspendedWithActiveTimer); |