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
Hi,
I'm using html-minifier-terser to handle HTML template literal, and define each template source using html as keyword. For some reason, I have to define customer col separately and repeated to generate col for few times. The following code snippet shows the simplest case I have, the output forces adding colgroup for col, which is not expected.
col element is a special case in htmlparser.js, if there's no colgroup in the same template then have to push one and trigger start with two tags (colgroup & col).
Is any chance to cover the case in the future?
Thanks
Version
V7.2.0
What browsers are you seeing the problem on?
Firefox, Chrome, Safari
Link to reproduce
No response
Relevant log output
No response
Willing to submit a PR?
None
The text was updated successfully, but these errors were encountered:
cWenyu
changed the title
[Bug]: wrap each col element in a colgroup when render col in a seperate function
[Bug]: wrap each col element in a colgroup when render col in a separate function
Jul 19, 2023
cWenyu
changed the title
[Bug]: wrap each col element in a colgroup when render col in a separate function
wrap each col element in a colgroup when render col in a separate function
Jul 21, 2023
What happened?
Hi,
I'm using
html-minifier-terser
to handle HTML template literal, and define each template source usinghtml
as keyword. For some reason, I have to define customer col separately and repeated to generate col for few times. The following code snippet shows the simplest case I have, the output forces adding colgroup for col, which is not expected.source code to be minified
minified output:
col element is a special case in
htmlparser.js
, if there's no colgroup in the same template then have to push one and trigger start with two tags (colgroup & col).Is any chance to cover the case in the future?
Thanks
Version
V7.2.0
What browsers are you seeing the problem on?
Firefox, Chrome, Safari
Link to reproduce
No response
Relevant log output
No response
Willing to submit a PR?
None
The text was updated successfully, but these errors were encountered: