[whatwg] Introducing new elements is expensive
ian at hixie.ch
Wed Mar 23 04:37:25 PST 2005
On Mon, 21 Mar 2005, Matthew Raymond wrote:
> > Elements inside <output> are rendered as elements, with all that that
> > implies; there is no special parsing.
> The contents of <output> are the initial value, yet they are not parsed.
By "no special parsing" I meant the parsing was the same as for, say, a
<span>. i.e. normal HTML parsing rules apply.
> > > Since we can't avoid a difference in rendering unless we
> > > artificially enforce a no-markup-inside-<output> rule, what does it
> > > hurt to simply have a |value| attribute to set the .defaultvalue
> > > directly?
> > The two things are separate. What's the use case for value=""?
> Well, for one, in situations where you want to use <input readonly> as a
> fallback container for a calculated value.
I don't really understand why you would both with <output> at all, in such
a case, since <input readonly> would work fine in both legacy and WF2 UAs.
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg