[whatwg] [wf2] 2.3. Changes to existing controls

On Wed, 26 Oct 2005, Anne van Kesteren wrote:
> Quoting Ian Hickson <ian at hixie.ch>:
> > > You should probably try harder ;-) Anyway, setting |value=""| on a form
> > > control should not result in the DOM attribute value being "on". It
> > > should result in it being "" and that should be submitted.
> > 
> > Ok. I agree with this. However, you go on to say:
> > 
> > > (Sections 2.3 and 2.4 have to be edited for this.)
> > 
> > I don't see anything in either 2.3 or 2.4 that contradicts what you said
> > above. This is why I was confused earlier, I guess. The bits you quoted in
> > your earlier mails agreed with what you were saying should happen, and
> > then you said they should change...
> 
> # A control is said to have no value selected if its value is the
> # empty string.
> 
> "empty string" was the bit I was falling over.

But that doesn't have any effect on radio buttons or check boxes. 
(Especially now that I've removed that odd example I mentioned.)


> > > It does not. Sorry about that. I just want to make it clear that XML 
> > > has some stupid rules authors should be aware about when dealing 
> > > with forms. This seemed like the most appropriate place to add the 
> > > note.
> > 
> > I don't see how these rules will affect users unless they go out of 
> > their way to make DTDs, in which case they deserve whatever they get.
> 
> The normalization happens without DTDs.

Well, yeah, the basic normalisation that happens to any attribute 
including HTML attributes and so forth. But the confusing normalisation 
only occurs with DTDs.

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

Received on Tuesday, 25 October 2005 16:21:47 UTC