- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 5 Sep 2013 13:52:19 -0700
- To: Ian Hickson <ian@hixie.ch>
- Cc: WHATWG <whatwg@lists.whatwg.org>, Boris Zbarsky <bzbarsky@mit.edu>
On Thu, Sep 5, 2013 at 1:47 PM, Ian Hickson <ian@hixie.ch> wrote: > On Thu, 5 Sep 2013, Boris Zbarsky wrote: >> On 9/4/13 8:07 PM, Ian Hickson wrote: >> > As far as I can tell, browsers keep treating it as an inline-block box >> > in those cases. >> >> OK, that works, I guess. That does mean that buttons are a replaced >> element, clearly, though... Something needs to spell that out. > > In what sense? > > The definition of "replaced element" here: > > http://www.w3.org/TR/CSS2/conform.html#replaced-element > > ...doesn't seem to apply to <button>. The rendering of <button> is very > much in CSS' scope, no? Technically, no, buttons are still replaced elements. In practice, buttons are pretty much stock CSS elements across all user agents, and we should probably standardize that. ~TJ
Received on Thursday, 5 September 2013 20:53:03 UTC