Project

Profile

Help

Bug #5796

closed

Can't catch `dblclick` event?

Added by Norm Tovey-Walsh about 1 year ago. Updated 12 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
2023-01-05
Due date:
% Done:

0%

Estimated time:
Applies to JS Branch:
Fix Committed on JS Branch:
Fixed in JS Release:
SEF Generated with:
Platforms:
Company:
-
Contact person:
-
Additional contact persons:
-

Description

No matter how fast I click the mouse, I get only single click events. I wonder if the answer lies here:

dblclick fires after two click events (and by extension, after two pairs of mousedown and mouseup events).

Actions #1

Updated by Martynas Jusevicius about 1 year ago

I think there are more events missing, e.g. selectstart.

Actions #2

Updated by Norm Tovey-Walsh about 1 year ago

On Slack, Pieter Lamers posts an example that works in Saxon 2.3. Did this get broken between 2.3 and 2.5?

Actions #3

Updated by Martynas Jusevicius about 1 year ago

My bad. It seems to work on a secod try.

Actions #4

Updated by Martynas Jusevicius about 1 year ago

onselectstart also works :facepalm:

Actions #5

Updated by Martynas Jusevicius 12 months ago

I think this one can be closed :)

Actions #6

Updated by Norm Tovey-Walsh 12 months ago

  • Status changed from New to Closed

Yes, I think so. What I discovered, but failed to add to this issue, is that in my testing, I'd created event handlers with the wrong mode names. I've updated the code that deals with events so that it warns if it encounters a mode name that's incorrect.

Please register to edit this issue

Also available in: Atom PDF Tracking page