Re: [WF2] new attributes that often conflict with actual pages

On Tue, 02 Dec 2008 11:25:50 +0100, Ian Hickson <ian@hixie.ch> wrote:

>> Obviously submitting forms randomly to wrong URLs makes any site where
>> users want to get things done *completely* useless.
>>
>> Bottom line: implementing "required" has been really painful
>> compatibility-wise. Any UA that wants to implement "required" as it is
>> specified now is going to need hackish workarounds against compat
>> problems.
>
> (Do you mean required or action? Or both?)

Oops, sorry to confuse you. I was looking up issues we've had with  
input@action and found some stuff about required too, so when typing the  
last paragraph I mixed them up. In the above paragraph I certainly meant  
"action" - not that "required" hasn't caused some pain but I think we've  
given feedback on "required" problems elsewhere in another thread.

> This is certainly problematic. It's unclear what we should do. It's hard
> to use another attribute name, since the whole point is reusing existing
> ones... can we trigger this based on quirks mode, maybe? Though I hate to
> add new quirks.

Sounds like a bad idea to me.

Would it be too weird to disallow relative URLs? If we say "attribute  
values that are not fully qualified URLs must be considered custom data  
and should not be considered during the submission process" or something  
to that effect?

In my personal opinion, I don't see why re-using attribute names is  
considered so important if we can find an alternative that feels memorable  
and usable. How does this look?

<input type="submit" formaction="http://www.example.com/">


-- 
Hallvord R. M. Steen
Core JavaScript tester, Opera Software
http://www.opera.com/
Opera - simply the best Internet experience

Received on Tuesday, 2 December 2008 13:14:04 UTC