[Bug 12241] Should form="" always make the input unassociated?

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12241

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #6 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-06-10 23:09:25 UTC ---
Apparently still no response from the vendor.

I guess we need to make a call on this. We have three options:

1. Leave it as is. One site break is known to break, but it's a conformance
error so careful authors will catch it. In this particular case it's also an
obvious typo in the source that is triggering this problem, so not breaking
something that had any good reason to be done in the past.

2. Make it a valid way to disassociate a form control. This will mean no
conformance error in some cases that break, but will add a new feature. Not
clear how useful the feature is, though.

3. Make it be ignored. This means we can no longer add the feature if it turns
out to be useful, but it fixes the one known broken site.

I'm leaning towards 1 right now.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Friday, 10 June 2011 23:09:28 UTC