Events Exception on IE

[mapher87@…]

trigger a list of objects return from a jQuery selector use '.click()' for exemple, will find some unexpected actions on IE, which display works well on FF. my code like this: $("#"+tableID+"_cb_"+pk).click(); bad action on IE, but FF; $("#"+tableID+"_cb_"+pk)[0].click(); done well;

[anonymous]

the problem occured when i try to use '.trigger("click")' instead of use '.click()', but it worked even worse for it couldn't be corrected.

[addyosmani]

Thanks for taking the time to contribute to the jQuery project! Please provide a reduced jsFiddle test case to help us assess your ticket! (in its current form, your code is incomplete).

Additionally, be sure to test against the jQuery Edge version to ensure the issue still exists. To get you started, use this boilerplate: ​http://jsfiddle.net/rwaldron/da3nM/. Open the link and click to "Fork" in the top menu.

[mapher87 <mapher87@…>]

js: function trMove(from_table, desti_table){ move <tr>s from one table to another, according to saved items; } function filter_td_click(td_self, pk){ function to trigger checkbox event

var tableID = $(td_self.parentNode.parentNode.parentNode).attr('id');td->tr->tbody|thead|tfoot->table; $("#"+tableID+"_cb_"+pk).cloick(); can only function at the first movement, at trMove() $("#"+tableID+"_cb_"+pk)[0].click();

} function on_checkboxChange(str_item){

saveChangeList(str_item, true); save changed items;

} html: <td><input type="checkbox" id="checked_field_cb_{{ checked_object.pk }}" class="for_checked" onclick="javascript: checkboxChange('{{ checked_object.pk }}')"/></td> <td class="clickable" onclick="javascript: filter_td_click(this, '{{ checked_object.pk }}')">{{ checked_object }}</td> >>>>>>>>>>>>>>>> i've downloaded jQuery.1.6.1, and test on the IE 7|8, the problem occurred again.

[trac-o-bot]

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!