Re: [whatwg] Introducing new elements is expensive

Anne van Kesteren wrote: Matthew Raymond wrote: By the way, is there a reason that can't have a |value| attribute? What if we want the initial contents on a legacy UA to be "Calculation Not Available", or perhaps an element like you suggest? Is this an example of Ian trying to avoid -style el

Re: [whatwg] Introducing new elements is expensive

Matthew Raymond wrote: By the way, is there a reason that can't have a |value| attribute? What if we want the initial contents on a legacy UA to be "Calculation Not Available", or perhaps an element like you suggest? Is this an example of Ian trying to avoid -style elements? From:

Re: [whatwg] Introducing new elements is expensive

Olav Junker Kjær wrote: The "output" element in WF2 shouldn't really be a new element. The semantics and interface are very similar to the input element (especially a input type=text with readonly). I suggest changing to . Only important difference is the fallback behavior. An element would n

Re: [whatwg] Introducing new elements is expensive

Ian Hickson wrote: I would recommend that suggestions avoid new elements, especially when those elements have a lot of attributes, and especially when the element has semantics very similar to an existing element. The "output" element in WF2 shouldn't really be a new element. The semantics and i