- From: Ilya Streltsyn via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Jan 2019 10:31:47 +0000
- To: public-css-archive@w3.org
@benface, the `display:inline` case for buttons is a bit special: it's a "final frontier" that is yet not achievable by CSS in any implementation. Implementers seem to have agreed that the ability to style buttons as flex or grid container is necessary, and at least Firefox has already implemented it somehow. But making a button display as a regular non-replaced non-atomic inline element is currently not achievable anywhere. That's why it was initially stressed in the title. @zcorpan, when I proposed `display:inline` as a hook for removing "magic" replaced-like behavior, I didn't realize that explicit and implicit change of `appearance` are equivalent, I assumed that explicit change has deeper effect. Sorry, it was my error. Now I believe that there probably should be two different values of `appearance` – the good old `none` to remove the platform-specific _default theming_ (borders, background, focus/hover highlighting etc.) while still preserving the "magic replaced-like" rendering behavior, and a new one to remove that "magic" altogether. -- GitHub Notification of comment by SelenIT Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3226#issuecomment-458489724 using your GitHub account
Received on Tuesday, 29 January 2019 10:31:48 UTC