- From: Roman Komarov via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Sep 2018 14:20:10 +0000
- To: public-css-archive@w3.org
@AmeliaBR thinking more about it: while I agree that this exact use case would “break”, for this use case the effect would be still minimal and acceptable, in my opinion. While not disappeared placeholder on whitespace input would be slightly confusing, it won't break anything — the field would work the same, the only slight annoyance would happen only if people would start writing a message from a whitespace, and the only case where this could be highly confusing is if the main/only purpose of the input would be to contain just whitespace, but the intersection of this exact use case and an `:empty` usage could be non-existent? So, while I generally prefer things to be backward-compatible, in this case, I don't see enough realistic use cases where things would break considerably, and the benefits of making the default behaviour more useful and less confusing would prevail over the minor annoyances it could cause. -- GitHub Notification of comment by kizu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1967#issuecomment-425110834 using your GitHub account
Received on Thursday, 27 September 2018 14:20:13 UTC