During the development of the CSS3 specification, the introduction of white-space-collapsing was considered.
Such a property will help solve the current general HTML / CSS problem .
Unfortunately, the current CSS3 specification no longer contains this property.
However, a similar property, which will also offer a solution to the problem mentioned above, now looks for CSS-text-4 , This time the working name for this property is text-space-collapse .
My question is: what were the reasons for not introducing white-space-collapsing in CSS3, but instead defer it to CSS-text-4?
EDIT: I'm looking for answers that
- are not speculative, therefore, the answers to them are based on publicly available sources (such as mailing lists, blog entries for the authors of the specifications, minutes of meetings of the authors of the specifications) or come directly from the authors of the specifications. (Some of them may already be registered here or someday registered here as it was in similar situations ).
- give a clear explanation or justification why this particular
white-space-collapsing has not yet been included in the CSS3 specification. (I really don’t understand this: what made the specification authors determine that the property was so incomprehensible that it had to be postponed to a later standard?) Therefore, I don’t look for too broad answers: “Well, sometimes specification writers just don’t feel that they the specification is completed in one way or another. " - should not be considered in fact part of the discussion of this topic. (Or put it another way: I do not ask how people feel that the property has been delayed. I just ask for a clear reason for this decision, as indicated by the specifiers. Therefore, if you read it literally, this question should not lead to a discussion of any issues.)
Discussions around these kinds of questions on Meta showed that this issue could be improved by providing him with a more practical point of view. So, another way to express this is: “If I were to implement a completely new browser or add new features to an existing one, why would I not want to implement the white-space-collapsing , as suggested in the earlier version of the CSS3 Specification?”
However, paraphrasing my original question in this way, it definitely becomes an invitation for opinions. And that's just not what I'm looking for. I am looking for an explanation of "past reasoning." So perhaps it’s better to say that this is the question: “Suppose I had to implement a completely new browser or add new features to an existing one. Now I don’t want to encounter problems / problems that CSS3 provided that removed the white-space-collapsing property from it white-space-collapsing during the specification development process. To avoid the foreseeable problems / problems when developing my browser: why didn't the specification developers include this property in the CSS3 specification?"
I know this question may be difficult to answer, but it definitely answers with a specific (and hopefully clear) answer.
A truly excellent answer to this question will include not only arguments in favor of this and relevant sources, but also some examples. An example of a great answer (to another similar question) can be found here: stack overflow