Bug 4948 – Incorrect HTML entity error recovery doesn't match other browsers

• Status: RESOLVED
• Resolution: FIXED
• Component: DOM

[Alexey Proskuryakov]

(from discussion in bug 4820)

Attached is a test matrix for invalid HTML entities with results for several browsers. Apparently, different 
browsers have little in common here, yet Safari matches none of them.

Perhaps, this should be improved.

[Alexey Proskuryakov]

Created attachment 3875 [details]
test matrix

[Eric Seidel (no email)]

What a great table.  The code for all this is inside htmltokenizer.cpp.

[Alexey Proskuryakov]

Bug 17689 has an example of this.

[Alexey Proskuryakov]

<rdar://problem/5827553>

[Sam Weinig]

This logic should be covered by http://www.whatwg.org/specs/web-apps/current-work/multipage/tokenization.html#consume 

[Adam Barth]

Our goal here is to match the HTML5 spec.  How does a WebKit nightly compare to Firefox 4 beta?

[Adam Barth]

Looks like we match Firefox 4 on everything except:

�
�
&#79228162514264337593543950433;
�

[David Kilzer (:ddkilzer)]

(In reply to comment #7)
> Looks like we match Firefox 4 on everything except:
> 
> �
> �
> &#79228162514264337593543950433;
> �

The above test cases match "Firefox (Mac)" column, and WebKit matches Firefox 33.1 except for these four cases (which look like regressions in Firefox per the chart):

� (0x100000061)
�
&#79228162514264337593543950433;
�

Marking as RESOLVED/FIXED.