W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2006

[whatwg] [wf2] changing the size DOM attribute of <select>

From: Jim Ley <jim.ley@gmail.com>
Date: Sat, 11 Feb 2006 00:24:31 +0000
Message-ID: <851c8d310602101624j7fea5610v95357b0a31d254f3@mail.gmail.com>
On 2/10/06, Anne van Kesteren <fora at annevankesteren.nl> wrote:
> Browsers disagree on what should be selected in such cases. Simple testcase:
>  <http://webforms2.testsuite.org/controls/select/009.htm>
> Opera 9 passes that test and I heard Safari nightlies do too. Internet Explorer
> and Firefox fail the testcase. Personally I would be in favor of changing the
> specification to be compatible with Opera 9 and Safari given that what they do
> is sensible.

Why can't this be left undefined? what does it matter to have
interopable rendering on invalid DOM changes?  Surely forcing code
changes on anyone is just a waste of implementation time here, not
updating the page when the DOM is changed to an invalid number is a
good optimisation?

IE for example simply rejects the update (the size remains at 2), that
seems like a sensible approach, as does normalizing it to 1.

I simply don't see the value in standardising the error behaviour here.

Received on Friday, 10 February 2006 16:24:31 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:45 UTC