CODEWITHSUNDEEP
javascriptspringinternet-explorer-11jsp-tags
sandy
sandy

Reputation: 243

Difference between <html:hidden> and <input type="hidden"> on IE11

I have come across a strange issue which seems to be browser related(IE9 and lower vs. IE11), but would like to know why the strange behavior.

Issue Description:I use a spring framework and use its related taglibs to retrieve data on my JSP. There is a variable called index which I retrieve from the form and it used to be retrieved in the following manner. 

<html:hidden property="index" name="pdmAcctSuppressForm" />

Value for the above variable namely index was accessed in a javascript using the following code snippet.

var index = document.getElementById("index").value;

The javascript seems to work as expected and retrieves the actual value in all IE browsers until IE9, but seems to fail to work on IE11. document.getElementById("index") returns invalid on IE11.

Solution: The problem has been resolved by changing the above mentioned taglib implementation from <html:hidden property="index" name="pdmAcctSuppressForm" />

to

<input type="hidden" name="pdmAcctSuppressForm" value="${pdmAcctSuppressForm.index}" id="index"/>

I would like to know what has been changed on IE11 which renders the implementation unusable and also if the solution I have quoted is the right and efficient one.

Upvotes: 0

Views: 804

Answers (1)

T.J. Crowder
T.J. Crowder

Reputation: 1074949

The javascript seems to work as expected and retrieves the actual value in all IE browsers until IE9, but seems to fail to work on IE11.
...
I would like to know what has been changed on IE11 which renders the implementation unusable and also if the solution I have quoted is the right and efficient one.

You should have had that problem with IE8 as well. Through IE7, IE had a bug: It found elements using getElementById that didn't have the id you asked for, but did have a name that matched. That is, in IE8 and earlier:

<input name="foo">

...would be found by document.getElementById("foo").

This was a bug (although for a while Microsoft called it a feature, and documented it), and it was fixed.

More (on my blog):

Upvotes: 2

Related Questions