Side navigation
#863 closed bug (fixed)
Opened January 22, 2007 06:00PM UTC
Closed April 22, 2007 03:24AM UTC
click trigger works different in all but IE
| Reported by: | alex.lg | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 1.1.3 |
| Component: | event | Version: | 1.1 |
| Keywords: | diffence, IE6, FF | Cc: | |
| Blocked by: | Blocking: |
Description
[SVN Version 1159]
Running the Test-Suite in Firefox the Results are displayed as expected by the Test-Suite, finally displaying the result-page.
Running the same in IE6 opens the
http://diveintomark.org/page, which is caused by the first
click().called in the first test for
.toggle()
(Line 9 of
eventTest.js:
link.click().toggle(fn1, fn2).click().click().click().click().click();
Attachments (0)
Change History (6)
Changed January 23, 2007 02:54PM UTC by comment:1
| summary: | Different results in eventTest between IE6.x and FF1.5x → toggle/click broken in IE |
|---|
Changed January 24, 2007 05:29AM UTC by comment:2
| summary: | toggle/click broken in IE → toggle/click broken in all but IE |
|---|
It's actually the other way around - IE is the only browser that actually, correctly, triggers the click event on an anchor. We have to simulate the desired behavior in all other browsers.
Changed January 24, 2007 05:30AM UTC by comment:3
| summary: | toggle/click broken in all but IE → click trigger works different in all but IE |
|---|
Changed February 12, 2007 12:32PM UTC by comment:4
This code works in IE7 and FFX 1.5.0.9, but not in IE6:
In IE6, i do get into the "function()" part, it does find the element, but does NOT trigger the click event.
jQuery('ul.stap1Hulp > li > a').click(function() { jQuery('input[@name=' + this.id + ']').trigger('click'); });
Changed February 13, 2007 07:20AM UTC by comment:5
p.s. the element which does not work is a submit button (input[@type=submit]). If i trigger the "click" event nothing happens in IE6. There are multiple buttons of thesame type, all with different names. Since i can't change the underlying script, i don't know how the server side handles things. My guess is that it looks at the name of the pressed button.
I modified the testsuite to at least stop moving to the mentioned site. But the problem still exists, and due to the inconsitency with FF, it must be considered a bug.