W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2008

[whatwg] [WF2] backwards compatibility with values of custom required attributes

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 4 Nov 2008 02:12:16 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0811032246440.1237@hixie.dreamhostps.com>
On Fri, 4 Jan 2008, Hallvord R M Steen wrote:
>
> some code from airgreenland.com reminded me to bring up the discussion 
> of how to treat values of "required" attributes:
> 
> <input name="CONTROLGROUPCONTACT$ContactInputView$TextBoxAddressLine2"
> type="text" maxlength="52"
> id="CONTROLGROUPCONTACT_ContactInputView_TextBoxAddressLine2"
> class="w10" required="false" requiredError="Street address Field 2 is
> required.">
> 
> I've seen this before (and I'm sure many of you will recognise the 
> ASP.NET stuff). The problem is that <input required="false"> is treated 
> as <input required> by WF2 because the "false" value isn't recognised. I 
> think WF2 needs to do something sensible to ensure backwards 
> compatibility - ASP.NET form validation is going to cause us serious 
> problems otherwise.

I notice that Opera still supports required="" today. Did this turn out to 
be a surmountable problem?

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 3 November 2008 18:12:16 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:07 UTC