W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2005

[whatwg] Introducing new elements is expensive

From: Ian Hickson <ian@hixie.ch>
Date: Wed, 23 Mar 2005 12:37:25 +0000 (UTC)
Message-ID: <Pine.LNX.4.61.0503231235450.12561@dhalsim.dreamhost.com>
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.   `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 23 March 2005 04:37:25 UTC

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