Home/ Questions/Q 721203
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T05:50:48+00:00

Is there a workaround for Internet Explorer to implement the functionality offered by ‘this’

  • 0

Is there a workaround for Internet Explorer to implement the functionality offered by ‘this’ javascript keyword to get the dom element that triggered the event?

My problem scenario is :
I have a variable number of text fields in the html form, like 

<input type="text" id="11"/>  
<input type="text" id="12"/>

..

I need to handle the “onchange” event for each text field, and the handling is dependent on the ‘id’ of the field that triggered the event.
So far I understand that my options are:
1) attach a dedicated event handler for each text field. so if I have n fields, i have n different functions, something like:

<input type="text" id="11" onchange="function11();"/>  
<input type="text" id="12" onchange="function12();"/>

but the text fields are added and removed dynamically, so a better way would be to have one generic function instead.

2) use the ‘this’ keyword like:

<input type="text" id="11" onchange="functionGeneric(this);"/>  
<input type="text" id="12" onchange="functionGeneric(this);"/>

But this option does not work with Internet Explorer.

Can anyone suggest a work around for getting it work in IE or some other solution that can be applied here?
Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I can’t reproduce your problem. Here’s an SSCCE based on the latest information in comments:

    <!doctype html>
<html lang="en">
    <head>
        <title>SO question 2618458</title>
        <script>
            function functionGeneric(id) {
                alert(id); // Shows either 11 or 12 correctly.
            }
        </script>
    </head>
    <body>
        <input type="text" id="text_11" onchange="functionGeneric(this.id.split('_')[1]);"/>  
        <input type="text" id="text_12" onchange="functionGeneric(this.id.split('_')[1]);"/>
    </body>
</html>

    It works fine in all major browsers I have here. Your actual problem lies somewhere else. Until you come up with more detail, or better, an SSCCE, it’s shooting in the dark to the root cause.

    • 0