none
IE11 and multiple password text boxes

    Question

  • I am experiencing an odd issue in IE11. We have a form with a plain text Account Number text box and 2 password text boxes (PIN and Password).

    When I fill out the form and hit submit, I can see in the DEV tools that only the Account Number and PIN are being submitted. The last text box (Password) is completely blank in the request.

     

    If I change the Account Number text box to a password type, the form submits correctly. If I change the Password text box to a plain text box, it submits correctly.

     
    This works fine in all other versions of IE.

    Do you know of any issues with a form with multiple password type text boxes in IE11?



    • Edited by BS Martin Friday, July 5, 2013 6:40 PM
    Friday, July 5, 2013 6:39 PM

Answers

All replies

  • Hi,

    You will find a link to the API reference at the top of these MSDN forums.

    http://msdn.microsoft.com/library/ie/hh828809(vs.85)

    without code it is the best we could offer without a wild guess.

    My guess... you have duplicate name or id attribute values.... validate and correct at validator.w3.org


    Rob^_^

    • Marked as answer by Yanping Wang Monday, July 15, 2013 9:13 AM
    Saturday, July 6, 2013 1:09 AM
  • Hi,

    I am seeing this issue on IE 11 and could reproduce with a simple form based HTML. Is this a bug in IE 11, because it works with older versions and other browsers.

    Note: I have used the method 'get' instead of 'post' to see the submit issue in the address bar url itself.

    <html>
    <body>
    <form id="frmNewUser_3" autocomplete="off" name="frmNewUser" action="http://1.1.1.1" method="get">
    <table id="TABLE_2" border="0" cellpadding="2" cellspacing="0">
    <tr>
            <td nowrap >Username:</td>
            <td>test</td>
            <td>&nbsp;</td>
    </tr>
    <tr>
            <td nowrap >Full Name:</td>
            <td><input id="name_39" type="text" name="name" maxlength="128" size="20" value="Unspecified Name"></td>
            <td>&nbsp;</td>
    </tr>
    <tr>
            <td nowrap >Password:</td>
            <td><input id="passwd_2" type="password" size="20" name="passwd" value=""></td>
            <td>&nbsp;</td>
    </tr>
    <tr>
            <td nowrap >Confirm Password:</td>
            <td><input id="confirm_passwd_2" type="password" size="20" name="confirm_passwd" value=""></td>
            <td>&nbsp;</td>
    </tr>
    <tr>
            <td>&nbsp;</td>
            <td>&nbsp;</td>
            <td>&nbsp;</td>
    </tr>
    </table>
    <td colspan="2"><input id="btnEdit_1" type="submit" name="btnEdit" value="Save Changes">&nbsp;</td>
    </form>
    </body>
    </html>
    

    - Deepesh

    Friday, August 23, 2013 5:45 AM
  • Hi,

    Please start your own questions if the offered answer does not satisfy your own question.

    Please validate and correct your markup at validator.w3.org/check.

    the following errors need to be addressed.

    Line 1, Column 1: no document type declaration;
    implying "<!DOCTYPE HTML SYSTEM>"
    <html>

    The checked page did not contain a document type ("DOCTYPE") declaration. The
    Validator has tried to validate with a fallback DTD, but this is quite likely to
    be incorrect and will generate a large number of incorrect error messages. It is
    highly recommended that you insert the proper DOCTYPE declaration in your
    document -- instructions for doing this are given above -- and it is necessary
    to have this declaration before the page can be declared to be valid.

  • Error Line 2, Column 6: document type does not allow element "BODY" here
    <body>

    The element named above was found in a context where it is not allowed. This
    could mean that you have incorrectly nested elements -- such as a "style"
    element in the "body" section instead of inside "head" -- or two elements that
    overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents.
    Due to HTML's rules of implicitly closed elements, this error can create
    cascading effects. For instance, using XHTML's "self-closing" tags for "meta"
    and "link" in the "head" section of a HTML document may cause the parser to
    infer the end of the "head" section and the beginning of the "body" section
    (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 3, Column 38: there is no attribute "AUTOCOMPLETE"
    <form id="frmNewUser_3" autocomplete="off" name="frmNewUser" action="http://1.1…

    You have used the attribute named above in your document, but the document
    type you are using does not support that attribute for this element. This error
    is often caused by incorrect use of the "Strict" document type with a document
    that uses frames (e.g. you must use the "Transitional" document type to get the
    "target" attribute), or by using vendor proprietary extensions such as
    "marginheight" (this is usually fixed by using CSS to achieve the desired effect
    instead).

    This error may also result if the element itself is not supported in the
    document type you are using, as an undefined element will have no supported
    attributes; in this case, see the element-undefined error message for further
    information.

    How to fix: check the spelling and case of the element and attribute,
    (Remember XHTML is all lower-case) and/or check that they are both allowed in
    the chosen document type, and/or use CSS instead of this attribute. If you
    received this error when using the <embed> element to incorporate flash
    media in a Web page, see the FAQ item on
    valid flash
    .

  • Error Line 31, Column 16: document type does not allow element "TD" here
    <td colspan="2"><input id="btnEdit_1" type="submit" name="btnEdit" value="Save …

    The element named above was found in a context where it is not allowed. This
    could mean that you have incorrectly nested elements -- such as a "style"
    element in the "body" section instead of inside "head" -- or two elements that
    overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents.
    Due to HTML's rules of implicitly closed elements, this error can create
    cascading effects. For instance, using XHTML's "self-closing" tags for "meta"
    and "link" in the "head" section of a HTML document may cause the parser to
    infer the end of the "head" section and the beginning of the "body" section
    (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 34, Column 7: end tag for "HTML" which is not finished
    </html>

    Most likely, you nested tags and closed them in the wrong order. For example
    <p><em>...</p> is not acceptable, as <em> must be closed
    before <p>. Acceptable nesting is:
    <p><em>...</em></p>

    Another possibility is that you used an element which requires a child
    element that you did not include. Hence the parent element is "not finished",
    not complete. For instance, in HTML the <head> element must contain a
    <title> child element, lists require appropriate list items (<ul>
    and <ol> require <li>; <dl> requires <dt> and
    <dd>), and so on.


  • Rob^_^

Monday, August 26, 2013 3:49 AM
  • Hello,

    Thanks for your feedback!  The engineering team is looking into this.

    Amy Adams [MSFT]

    • Proposed as answer by EricLaw [Edge] Tuesday, September 3, 2013 9:40 PM
    Tuesday, September 3, 2013 6:33 PM
  • Maybe you can insert a <input type="text"> element before the password element......
    Thursday, September 5, 2013 8:49 AM