Skip to content
This repository has been archived by the owner on Jul 30, 2019. It is now read-only.

More detailed explanation of U+0000 handling #1117

Merged
merged 1 commit into from
Jan 14, 2018
Merged

More detailed explanation of U+0000 handling #1117

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 5 additions & 11 deletions sections/syntax.include
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,14 +1,9 @@
<section>
<!--
██ ██ ████████ ██ ██ ██ ██████ ██ ██ ██ ██ ████████ ███ ██ ██
██ ██ ██ ███ ███ ██ ██ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██
██ ██ ██ ████ ████ ██ ██ ████ ████ ██ ██ ██ ██ ██ ██
█████████ ██ ██ ███ ██ ██ ██████ ██ ██ ██ ██ ██ ██ ██ ███
██ ██ ██ ██ ██ ██ ██ ██ ██ ████ ██ █████████ ██ ██
██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███ ██ ██ ██ ██ ██
██ ██ ██ ██ ██ ████████ ██████ ██ ██ ██ ██ ██ ██ ██ ██

HTML SYNTAX - Parsing...

-->
<!-- This section ostensibly kept up to date by travil@microsoft.com -->

<dfn>The HTML syntax</dfn> {#syntax}
==========================
Expand Down Expand Up @@ -1402,9 +1397,8 @@
real character in the stream, but rather the lack of any further characters.

<p class="note">The handling of U+0000 NULL characters varies based on where the characters are
found. In general, they are ignored except where doing so could plausibly introduce an attack
vector. This handling is, by necessity, spread across both the tokenization stage and the tree
construction stage.</p>
found. In general, they are ignored, but for security reasons they are sometimes replaced with
U+FFFD REPLACEMENT CHARACTER. This can happen in tokenization or tree construction.</p>

### Parse state ### {#parse-state}

Expand Down