You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
he.decode('&abc;', {strict: true}) throws error with this message: Parse error: named character reference was not terminated by a semicolon, when in fact neither a nor ab are valid legacy named character references and &abc; is terminated by ;. I think an error message to the effect of Parse error: named character reference is not spec-defined would be better in this case.
This and #50 notwithstanding, he has been a great companion to the HTML5 spec as I learn about and write a spec-compliant HTML entity decoder for Swift :)
The text was updated successfully, but these errors were encountered:
Version 1 supports HTML4 named character references; I'm currently working on version 2 which will support HTML5 named character references and improve parsing to detect parse errors as defined in the spec.
A minor issue:
he.decode('&abc;', {strict: true})
throws error with this message:Parse error: named character reference was not terminated by a semicolon
, when in fact neithera
norab
are valid legacy named character references and&abc;
is terminated by;
. I think an error message to the effect ofParse error: named character reference is not spec-defined
would be better in this case.This and #50 notwithstanding,
he
has been a great companion to the HTML5 spec as I learn about and write a spec-compliant HTML entity decoder for Swift :)The text was updated successfully, but these errors were encountered: