CSS Minification with clamp()

Develop, Build & Integrate CMS Development
1

When my CSS is minified it is having the whitespaces in the clamp() function removed, making it a invalid property.

clamp(21px,15.5454545455px+1.7045454545vw,33px)

It should be like this

font-size: clamp(21px,15.5454545455px + 1.7045454545vw,33px);

Is there any way I can ensure the whitespace remains here after minification?

This is also the case in here - “I figured this out by using the ?hsDebug=true in our url(s) to see what hubspot is doing. Sure enough, it looks like the hubspot minifier is killing the property, since the css works fine in debug mode.”

2

@dennisedson potentially similar to this Tailwind minification issue?

3

@MWyatt , @piersg I can reproduce the issue in my portal. Am getting some additional eyes on it

@MWyatt ,

15.5454545455px + 1.7045454545vw

were you challenging yourself to see how many decimal points you could get in there :upside_down_face:

4

Following up here,

There is an issue with the current minfier which is causing the issue. There is an new minifier on the horizon, but not quite ready yet. We are going to patch the present minifier to accomodate for this issue. Patch should be issues shortly. @MWyatt thanks for bringing this issue up.

5

Subpixels at geo coordinate precision levels… There’s something you don’t see every day. Some light reading for the technical bits of why such precision is pointless if interested:

https://ieeexplore.ieee.org/document/8766229

https://en.wikipedia.org/wiki/Font_rasterization

https://en.wikipedia.org/wiki/Sub-pixel_resolution

https://en.wikipedia.org/wiki/Subpixel_rendering

https://en.wikipedia.org/wiki/Font_hinting

Of historical interest… On legacy browsers and modern ones the variations in subpixel rendering is quite interesting.

source.gif

6

Fix has been deployed. Will need to republish the file to be reminified