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
The fact that this generates invalid HTML is not in itself a problem. You'll always be able to create invalid HTML by inserting raw HTML. And the example is flagged as a case where you get "surprising" results; this is almost certainly not something someone would do intentionally, but it's still useful to illustrate what the spec's rules call for here.
One thing that could be changed in our current rules: </td> starts a raw HTML block, per start condition 6, but </pre> does not. That may be surprising, but it's due to the special treatment of pre, style, and script in the start/end conditions.
If we added a condition that a line beginning with </pre> starts a raw HTML block, then we'd get the result you describe above.
http://spec.commonmark.org/0.28/#example-116 introduced in #459 adds an example that requires to generate a broken HMTL.
Input:
Expected in the spec:
Suggested fix:
The text was updated successfully, but these errors were encountered: