[whatwg] prefilling select

Ian Hickson ian at hixie.ch
Sat Aug 28 06:29:39 PDT 2004

On Sun, 22 Aug 2004, [ISO-8859-1] Olav Junker Kjær wrote:
>> What makes you think the first case is synchronous?
> Section 6.1 says:
> "If a select element or a datalist element being parsed has a data attribute,
> then as soon as the element and all its children have been parsed and added to
> the document, it should be prefilled."
> Maybe this should be rephrased to indicate that the UA should begin fetching
> data at this point, but the actual prefilling may happen later?

Yeah, good call.

> In section 6.2 it says:
> "Before load events are fired, but after the entire document has been parsed
> and after select elements have been filled from external data sources (if
> necessary), forms with data attributes are prefilled."
> Does that mean that the data should start loading at this time, but the
> prefilling may finish later, after onload has fired? If this is the case,
> maybe it would be useful with an event ("onprefilled"?) to fire when the form
> is prefilled. Often you would want to have the form disabled until it has
> finished prefilling.

I wanted onload to happen after all the prefilling. I've clarified t.

>>> Maybe it would be more natural to use a method called loadData(uri) or 
>>> something like that.
>> We could do... What would setting the data attribute do? Nothing?
> Maybe it could be read-only?

You can't make attributes read-only, they are always mutable using the 
setAttribute() method.

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

More information about the whatwg mailing list