Back in 2017, it was resolved to defer the fit-content keyword level 4 of the Sizing spec. together with the stretch keyword.
Though it looks like in the meantime all major browser engines implemented this keyword already. Interestingly, they don't support the stretch keyword yet while the spec. refers to fit-content being equivalent to fit-content(stretch) (which is actually not allowed at the moment, because fit-content() currently only takes a <length-percentage>).
At the same time, the fit-content() function is not supported by any browser so far. There's only an experimental implementation in Firefox.
So, fit-content doesn't seem to be dependent on fit-content().
Therefore, I suggest to revert the resolution of #1912 and move the fit-content keyword back to level 3, and instead defer the fit-content() function to level 4.
Sebastian
Back in 2017, it was resolved to defer the
fit-contentkeyword level 4 of the Sizing spec. together with thestretchkeyword.Though it looks like in the meantime all major browser engines implemented this keyword already. Interestingly, they don't support the
stretchkeyword yet while the spec. refers tofit-contentbeing equivalent tofit-content(stretch)(which is actually not allowed at the moment, becausefit-content()currently only takes a<length-percentage>).At the same time, the
fit-content()function is not supported by any browser so far. There's only an experimental implementation in Firefox.So,
fit-contentdoesn't seem to be dependent onfit-content().Therefore, I suggest to revert the resolution of #1912 and move the
fit-contentkeyword back to level 3, and instead defer thefit-content()function to level 4.Sebastian