10332 2010-08-09 19:09:23 +0000 Shipping browsers don't have form.action reflect the DOM attribute exactly. Specifically, if the content attribute is the empty string, they generally return "" on an IDL get, not the current address. This contradicts the spec, but it would be confusing 2010-10-04 14:48:26 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other CLOSED INVALID http://www.whatwg.org/specs/web-apps/current-work/#form-submission-0 NE P3 normal --- 1 contributor ian annevk ayg mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 37313 0 contributor 2010-08-09 19:09:23 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#form-submission-0 Comment: Shipping browsers don't have form.action reflect the DOM attribute exactly. Specifically, if the content attribute is the empty string, they generally return "" on an IDL get, not the current address. This contradicts the spec, but it would be confusing to behave like the spec demands, because <form action=""> is magic -- it ignores <base>. It would probably make the most sense to say that doing an IDL get on action for <form action=""> should return the current document's address (where it will be submitted), not whatever "" resolves to (as the spec says) and not literally "" (as most browsers currently do). (Firefox 4, Chrome dev, WebKit nightly, and Opera 10.60 all return literally "" here, although in the case of WebKit and Opera it seems to be part of larger errors in URL reflection. See old Mozilla bug on this issue: https://bugzilla.mozilla.org/show_bug.cgi?id=297761) Posted from: 68.175.61.233 38386 1 ayg 2010-09-01 22:40:07 +0000 Okay, never mind. All browsers other than IE just reflect this as a string, not a URL. I'll update bug 10331 with the info, since this is really part of that.