Issue metadata
Sign in to add a comment
|
HTML is parsed in text/plain documents |
||||||||||||||||||||
Issue descriptionVersion: 54.0.2823.0 OS: Only tested on macOS 10.11.6 so far What steps will reproduce the problem? (1) Run with '--enable-features=ParseHTMLOnMainThread<ParseHTMLOnMainThread' '--blink-settings=parseHTMLOnMainThreadSyncTokenize=true' (but this showed up in my Canary organically). (2) Go to URL `data:text/plain,<b>bold?!</b>`. What is the expected output? A page with the literal text `<b>bold?!</b>`. What do you see instead? The text `bold?!`, in a bold font.
,
Aug 13 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/5a5b7beccee1f245d245eed92f4b5f591b841b4f commit 5a5b7beccee1f245d245eed92f4b5f591b841b4f Author: csharrison <csharrison@chromium.org> Date: Sat Aug 13 19:14:44 2016 [ParseHTMLOnMainThread] Force plaintext synchronously on lookahead parser BUG= 635634 Review-Url: https://codereview.chromium.org/2223223002 Cr-Commit-Position: refs/heads/master@{#411900} [add] https://crrev.com/5a5b7beccee1f245d245eed92f4b5f591b841b4f/third_party/WebKit/LayoutTests/fast/parser/force-plaintext.html [modify] https://crrev.com/5a5b7beccee1f245d245eed92f4b5f591b841b4f/third_party/WebKit/Source/core/html/parser/HTMLDocumentParser.cpp
,
Aug 13 2016
,
Aug 15 2016
Verified happy in Canary 54.0.2829.0! Thanks for the quick fix. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by csharrison@chromium.org
, Aug 8 2016Status: Started (was: Assigned)