Skip to main content

Bug Tracker

Side navigation

#1382 closed bug (invalid)

Opened July 10, 2007 01:45AM UTC

Closed November 29, 2007 05:22PM UTC

dblclick() handler not called in Konqueror 3.5.7

Reported by: sgbeal Owned by:
Priority: major Milestone: 1.2.2
Component: event Version: 1.1.3
Keywords: Cc:
Blocked by: Blocking:
Description

Hiya!

It would seem that adding a .dblclick() handler is useless in konqueror 3.5.7 (don't know about other versions). A .click() handler works fine, but a .dblclick() handler is never called (same code works in Firefox 2.0.0.4, though).

i've tried both 1.1.3.1 and the latest CVS code (as of 02:00 GMT+1, 10th July 2007).

A test case is attached, but you must replace the internal jquery.pack.js URL with your own.

Err.... creating the ticket with attachment FAILED due to lack of space on the target drive. So i'm pasting in the test case code here:

<script type='text/javascript'>

 $(document).ready(function(){
	$('#DoubleClickTest').dblclick(function(){
		alert("Double-click handler called.");
	});
});
</script>

<div id='DoubleClickTest'>double-clicking this field should pop up an alert()</div>

In Firefox 2.0.0.4 that calls alert() on a dblclick, but in konqi the handler is never called.

Attachments (1)
  • dblclick-confirm.html (1.3 KB) - added by sgbeal July 10, 2007 01:46AM UTC.

    let's see if drive space error is gone...

Change History (2)

Changed July 11, 2007 06:46PM UTC by sgbeal comment:1

Sorry about the multiple postings of this record - my post kept timing out, and i wasn't sure if it got posted. The "view my tickets" feature silently fails, so i didn't find the dupes.

Changed November 29, 2007 05:22PM UTC by davidserduke comment:2

milestone: 1.1.41.2.2
resolution: → invalid
status: newclosed

At this time Konqueror is not a supported browser as can be seen here:

http://docs.jquery.com/Browser_Compatibility

There have been some code changes so this might be fixed but, unfortunately, I don't have this browser to test. If you find it IS fixed, please reopen the bug and I'll close it as such. But for now I'm going to close it as invalid since it isn't a supported browser.