- From: <bugzilla@jessica.w3.org>
- Date: Fri, 02 Dec 2011 18:02:07 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12561 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #37 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-12-02 18:02:04 UTC --- EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: Let's cut to the chase here. We can't allow action="" with no value because it's too confusingly similar to action=" " with a space which has different behaviour. We can't make action="" and formaction="" different because that would be ridiculously confusing. For almost all purposes, if you want to target the same page you can use target="?" or formaction="?". Sure, there might be cases where that isn't quite as convenient as you might like, e.g. because you're POSTing to a URL with query parameters. So don't do that. Put the data in the POST payload, or in the path, or don't use both action="" and formaction="" in such situations. -- Configure bugmail: https://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, 2 December 2011 18:02:11 UTC