Summary: | [testcase] Adding a unknown event listener makes this script return the wrong onclick value | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Aldrik <Aldrik> |
Component: | khtml ecma | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | maksim, zahl |
Priority: | NOR | ||
Version: | 3.5 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | The above testcase so you can easily go clicky click |
Description
Aldrik
2007-06-15 16:58:42 UTC
Doesn't have to be unknown, any addEventListener would do, I think --- it gets confused because the same listener function is used as both a legacy HTML-style listener and real one.. That code looks bogus, but I don't know what it's trying to do.. Right you are any event messes it up (sorry I should have tested with some standard ones). Bogus code? Yeah I was just trying to show the bug, the propper script was a custom event listener & DOMReady script, which I then decided I'd make it trigger the click even of any #bookmark in the URL after the DOMReady scripts had loaded (it works quite nicely if I do say so myself :)). Anyway none of the other browser I tested in (FF and Opera) have a problem with this. I've already worked around it, I just thought you amazing KDE Dev's (I'm a big fan ;)) would want to know. By bogus code I meant the one in KHTML, not your example :-) Created attachment 24507 [details]
The above testcase so you can easily go clicky click
same testcase, easier to click
Is this supposed to work now?
fixed in SVN by vtokarev |