This was working fine recently, now today it stopped working, first using version 0.86 extended, as well as after a Manjaro update today which bumped it to 0.87.0. This seems to be the case for me whether I continue to use the minifyOutput = true method I prefer in config, or whether I use the --mi…

Yes, the default behaviour is changed: Minify.html, make keepWhitespace = true default opened 09:03AM - 19 Jul 21 UTC (UTC) closed 09:35PM - 19 Jul 21 UTC (UTC) [bep] …

Thanks. That gets me a little further along, but it still doesn’t strip every last bit of whitespace. I don’t understand why anyone felt the need to change that behavior, you can see HTML not minified in development, and if you really are hell bent on un-minifying it in production, there’s, e.g., t…

[image] ddg: I don’t understand why anyone felt the need to change that behavior See [image] Change how spaces are handled support I am not sure exactly when this started to happen but I recently switched to 0.84 and then 0.85 and noticed that in many of my templat…

In this example from my own site (see screenshot), I understand wanting to preserve, say, the spaces in </a> | <a> (in both the markup and the rendered page), but not the line breaks before | <a> in the markup. The line breaks were only for my own pre-minify benefit in a text editor and my git repo…

At a guess those spaces a preserved because (sadly) they affect the resulting layout (yes, really; HTML is oddly spec’d). EDIT: That is spaces between tags can affect layout.

You need to understand how go-html-templates work. Everything you write in your templates is printed out “as is”. If you want to remove “whitespaces” you need to use the proper template tags. You might have the following template: {{ range something }} {{ .title }} {{ end }} and this will resul…

Thanks. I gave in and converted the nav menu to <li> items to make one issue go away. But to give an example of something that, while not crucial, confuses me nonetheless, here is my sample template: <!DOCTYPE html> <html lang="{{ .Site.LanguageCode }}"> {{/* <head> {{- partial "he…

If the line breaks were not preserved the browser would display this: [image] instead of this: [image] You might find this useful: https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model/Whitespace

It’s just too bad the minifier does not mimic the browser rendering engine (or perhaps does not do it consistently). From the article you linked: Next, line breaks are converted to spaces So if the minifier cannot figure out to also discard newline 2, newline 3 and so forth within a <p>, then i…

Between item 1 and the pipe, there must be one whitespace character. Whether the character is an actual space or a newline doesn’t matter. I suspect if you examine the source carefully you will find that there are no spaces after the 1. If there are, you can file a bug with tdewolf/minify.

[image] carlmjohnson: Between item 1 and the pipe This issue @ddg raises is between the <p> and ‘item 1’.

Is HTML minification broken?

support

chrillek August 10, 2021, 8:10am 4

See

Topic		Replies	Views
"hugo --minify" strips spaces and preserve some new lines support	7	1578	March 15, 2021
Change how spaces are handled support	1	842	July 15, 2021
Indentation isn't stripped from minified HTML like it is for minified XML support	8	179	March 3, 2025
`hugo --minify` strips out `</p>` tags support	31	3876	September 13, 2018
Whitespaces even in a minified build?	8	814	March 25, 2021

Is HTML minification broken?

Related topics