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
lone surrogates are invalid utf8, so html5gum 0.3.0, which takes &str/String, is not able to handle those.
after merging #25, html5gum will be able to read arbitrary bytes. at this point the expectation might be that lone surrogates produce error tokens, but they do not.
note: lone surrogates have no impact on parsing behavior. only some error tokens are missing from token stream.
The text was updated successfully, but these errors were encountered:
html5gum assumes that the incoming bytestream is mostly valid UTF-8. The spec says that lone surrogate should create an error, and currently they don't. I don't need to worry beyond that.
lone surrogates are invalid utf8, so html5gum 0.3.0, which takes
&str
/String
, is not able to handle those.after merging #25, html5gum will be able to read arbitrary bytes. at this point the expectation might be that lone surrogates produce error tokens, but they do not.
note: lone surrogates have no impact on parsing behavior. only some error tokens are missing from token stream.
The text was updated successfully, but these errors were encountered: