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
This is following on from my comment here: #45 (comment)
I've done a little more experimenting and discovered that certain html tags work inside <object> tags and others don't (they are moved to after the object tag).
For example, <img>, <span> and <i> all work ok, but <p> and <div> don't, i.e. inline level elements work, but not block level.
Having read up a little more on the <object> tag apparently you are allowed zero, or any number of <param> elements, plus 'transparent' content, i.e. content that is valid HTML5 even if these tags are removed.
I suspect therefore, that html-minifier is acting as intended and merely respecting valid html markup, but if you have any other insight into this I'd love to know :)
The text was updated successfully, but these errors were encountered:
I think this is because some tags are wrongly registered in htmlparser. I have the same problem with the <iframe> tag. This one as well as the <object> tag are registered as block level (correct) as well as inline elements (wrong). If you remove them from the inline list in htmlparser.js, it works fine.
This is following on from my comment here: #45 (comment)
I've done a little more experimenting and discovered that certain html tags work inside
<object>
tags and others don't (they are moved to after the object tag).For example,
<img>
,<span>
and<i>
all work ok, but<p>
and<div>
don't, i.e. inline level elements work, but not block level.Having read up a little more on the
<object>
tag apparently you are allowed zero, or any number of<param>
elements, plus 'transparent' content, i.e. content that is valid HTML5 even if these tags are removed.I suspect therefore, that html-minifier is acting as intended and merely respecting valid html markup, but if you have any other insight into this I'd love to know :)
The text was updated successfully, but these errors were encountered: