- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Thu, 12 Apr 2018 14:02:17 +0000
- To: public-css-archive@w3.org
> And this is showing the main problem - you don't know [...] You are under the impression that I am personally trying to kill this. I am not. There are many things that I don't know. But my personal lack of knowledge is not the cause of this. Every single time this has been discussed in the CSS-WG, the **only** justification that was brought up was compatibility. Based on that, the working group (not me) decided that we should specify it **only if** browsers that currently do not implement it are forced to do so due to compatibility bugs. An incomplete definition was later added to the specification by mistake, against the decision of the group, and then removed when noticed. This remains the status to this day. I was merely following up on an existing group decision, by saying that implementations and specs should match, so it needs either to be added to all implementations and to the spec OR removed from the implementations that have it. You are arguing that `word-break:break-word` should exist for other reasons than just compatibility. I am not saying that you are wrong. I am saying that if you want to convince the group to add this property to the specification, the most useful thing to do is not to be angry at me, but to explain in detail all the cases where you think this is a desirable property. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2390#issuecomment-380815866 using your GitHub account
Received on Thursday, 12 April 2018 14:02:26 UTC