[Bug 10332] New: 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

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

           Summary: 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
           Product: HTML WG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#for
                    m-submission-0
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html@w3.org


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

-- 
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 Monday, 9 August 2010 19:09:25 UTC