On Mon, 2 May 2011, Boris Zbarsky wrote:
On 5/2/11 7:26 PM, Ian Hickson wrote:
I think it'd be better for [the rendering of options in a select
being one to a line] to be a style scoped to the binding that defines
the select, personally.
OK, but more on this below.
I would
On Tue, 4 Jan 2011, Boris Zbarsky wrote:
On 1/4/11 7:47 PM, Ian Hickson wrote:
1) Gecko makes optgroup and option blocks (and applies some
bold/italic/font-size styles to the optgroup, at least).
2) Presto renders the text in theoptgroup (which it treats as an
inline) but
On 5/2/11 7:26 PM, Ian Hickson wrote:
That makes sense, though I think it'd be better for that to be a style
scoped to the binding that defines theselect, personally.
OK, but more on this below.
I would clearly prefer that the behavior be defined in terms of CSS; UAs
that under the hood want
On Wed, 20 Oct 2010, Boris Zbarsky wrote:
Consider the following testcase (XHTML, but an equivalent DOM can be
constructed in HTML, of course).
!DOCTYPE html
html xmlns=http://www.w3.org/1999/xhtml;
body
aaa
optgroup
bbb
/optgroup
ccc
option
ddd
On 1/4/11 7:47 PM, Ian Hickson wrote:
1) Gecko makes optgroup and option blocks (and applies some
bold/italic/font-size styles to the optgroup, at least).
2) Presto renders the text in theoptgroup (which it treats as an
inline) but doesn't render theoption at all.
3) Webkit
Consider the following testcase (XHTML, but an equivalent DOM can be
constructed in HTML, of course).
!DOCTYPE html
html xmlns=http://www.w3.org/1999/xhtml;
body
aaa
optgroup
bbb
/optgroup
ccc
option
ddd
/option
eee
/body
/html
I observe the
