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
{{ message }}
This repository has been archived by the owner on Feb 2, 2021. It is now read-only.
produces a dom containing a p tag, e.g. <p a="b" ></p>
This seems like a minor issue, but it's a little bit weird. It's possible this is on purpose, but based on the comments, this looks like an oversight in the way the parser is seeking out the next '>' token.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In https://github.com/google/caja/blob/27248d0f223038346d63278b52ec038e77418ba9/src/com/google/caja/plugin/html-sanitizer.js when using
javascript function parse(htmlText, handler, param) {
in
javascript parseTagAndAttrs(parts, pos) {
The two badly formed html strings produce different output:
produces an empty dom
produces a dom containing a p tag, e.g.
<p a="b" ></p>
This seems like a minor issue, but it's a little bit weird. It's possible this is on purpose, but based on the comments, this looks like an oversight in the way the parser is seeking out the next '>' token.
The text was updated successfully, but these errors were encountered: