Spacer block min size

[anonymized_17612203]

I used the spacer in the past with 1, 2, 3,... pixel size. Now it's only possible starting with 20 pixel. This is by far to much. This musst be possible with starting 1 pixel. With 20 pixel starting the spacer makes less sense.

Think that is a bug and not a changed function because there is no reason to set the min size up and also do to the fact, that it was at 1 pixel in the past.

I double checked this in a new WP installation. It's the case with and without having the Gutenberg plugin active.

[aduth]

Do you recall which version supported pixel values smaller than 20?

As best I can tell, it has (at least intended to) enforce a minimum of 20 pixels since its initial introduction in 2018:

​https://github.com/WordPress/gutenberg/pull/6121

Specifically:

• ​https://github.com/WordPress/gutenberg/pull/6121/files#diff-edc3bf1040e9511a3561114ec1e5dba5R46
• ​https://github.com/WordPress/gutenberg/pull/6121/files#diff-edc3bf1040e9511a3561114ec1e5dba5R84

[anonymized_17612203]

Hmmm.... don't know exactly, maybe I'm mixing this with Elemetor? There for sure it is possible to use 1 pixel. However, the past isn't interesting, what counts is the functionallity and I see no reason to change it to min 1 pixel. At the moment I can edit the spacer as html, change to 1 pixel, get an error and convert to html... then it is working. This shows me that there is no conflict outside the block, only the spacer block has an issue with itself :-)

[apedog]

Why would WordPress enforce a minimum height for spacers?

[anonymized_17612203]

Replying to apedog:

Why would WordPress enforce a minimum height for spacers?

Good question... There is no real reason. The only reason which came up was usability of the block in the backend. But this shouldn't be a reason. It should be possible to display the spacer block in thebackend (the editor) with a fixeed high and use the set high only for the frontend.

[talldanwp]

Now being tracked on ​https://github.com/WordPress/gutenberg/issues/21702