Re: [whatwg] We should not throw DOM Consistency and Infoset compatibility under the bus

2013-03-06 Thread Simon Pieters
On Wed, 06 Mar 2013 18:55:27 +0100, Ian Hickson wrote: On Wed, 6 Mar 2013, Simon Pieters wrote: On Mon, 14 Jan 2013 09:40:56 +0100, Henri Sivonen wrote: > Would it be terrible to make attempts to mutate the 'is' attribute > throw thereby teaching authors who actually try to mutate it that

Re: [whatwg] We should not throw DOM Consistency and Infoset compatibility under the bus

2013-03-06 Thread Ian Hickson
On Wed, 6 Mar 2013, Simon Pieters wrote: > On Mon, 14 Jan 2013 09:40:56 +0100, Henri Sivonen wrote: > > > Would it be terrible to make attempts to mutate the 'is' attribute > > throw thereby teaching authors who actually try to mutate it that it's > > not mutable? > > We already have several a

Re: [whatwg] We should not throw DOM Consistency and Infoset compatibility under the bus

2013-03-06 Thread Simon Pieters
On Mon, 14 Jan 2013 09:40:56 +0100, Henri Sivonen wrote: Would it be terrible to make attempts to mutate the 'is' attribute throw thereby teaching authors who actually try to mutate it that it's not mutable? We already have several attributes that are immutable but don't throw or anything w

Re: [whatwg] We should not throw DOM Consistency and Infoset compatibility under the bus

2013-01-14 Thread Henri Sivonen
On Fri, Jan 11, 2013 at 10:00 PM, Ian Hickson wrote: > On Fri, 11 Jan 2013, Henri Sivonen wrote: >> I understand that supporting XML alongside HTML is mainly a burden for >> browser vendors and I understand that XML currently doesn't get much >> love from browser vendors. > > Not just browser vend

Re: [whatwg] We should not throw DOM Consistency and Infoset compatibility under the bus

2013-01-11 Thread yuhong
Ian Hickson wrote: > > On Fri, 11 Jan 2013, Henri Sivonen wrote: >> Hixie wrote in https://www.w3.org/Bugs/Public/show_bug.cgi?id=18669#c31 : >> > I think it's fine for this not to work in XML, or require XML changes, >> > or use an attribute like xml:component="" in XML. It's not going to be

Re: [whatwg] We should not throw DOM Consistency and Infoset compatibility under the bus

2013-01-11 Thread Vipul S. Chawathe
>From: Ian Hickson [mailto:i...@hixie.ch] >To: Henri Sivonen >On Fri, 11 Jan 2013, Henri Sivonen wrote: >> Hixie wrote in https://www.w3.org/Bugs/Public/show_bug.cgi?id=18669#c31 : >> > I think it's fine for this not to work in XML, or require XML >> > changes, or use an attribute like xml:compon

Re: [whatwg] We should not throw DOM Consistency and Infoset compatibility under the bus

2013-01-11 Thread Ian Hickson
On Fri, 11 Jan 2013, Henri Sivonen wrote: > Hixie wrote in https://www.w3.org/Bugs/Public/show_bug.cgi?id=18669#c31 : > > I think it's fine for this not to work in XML, or require XML changes, > > or use an attribute like xml:component="" in XML. It's not going to be > > used in XML much anyway i

Re: [whatwg] We should not throw DOM Consistency and Infoset compatibility under the bus

2013-01-11 Thread David Young
On Fri, Jan 11, 2013 at 12:29:42PM +0200, Henri Sivonen wrote: > I think it would be a mistake to change HTML in such a way that it > would no longer fit into the XML data model *as implemented* and > thereby limit the range of existing software that could be used > outside browsers for working wit

[whatwg] We should not throw DOM Consistency and Infoset compatibility under the bus

2013-01-11 Thread Henri Sivonen
Hixie wrote in https://www.w3.org/Bugs/Public/show_bug.cgi?id=18669#c31 : > I think it's fine for this not to work in XML, or require XML changes, > or use an attribute like xml:component="" in XML. It's not going to > be used in XML much anyway in practice. I've already had browser > vendors ask m