Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#13475 closed bug (notabug)

mouse cursor position not accurately determined in jquery-ui.min.js for latest version 1.11.14

Reported by: smoitra Owned by:
Priority: minor Milestone: none
Component: ui.position Version: 1.11.4
Keywords: Cc:
Blocked by: Blocking:

Description

the position of the cursor is not accurate as calculated in jquery-ui.min.js. User expects the cursor tip to be the correct position but if the mouse cursor tip and the 2 right,left ends of the cursor are in different rows - then the position of the row is accurate. The jquery-ui.min.js is not giving the cursor tip position as the position of the row.

Let us say:the mouse cursor is overlapping 2 rows: X and X+1. The mouse cursor tip is pointing to row X The end points of the mouse cursor are pointing to row X+1 User expects RowX to be the correct position Actual behaviour: Row X+1 is retrieved from jquery-ui.min.js

Change History (3)

comment:1 Changed 4 years ago by Scott González

Resolution: notabug
Status: newclosed

The cursor is actually a single point, so it's impossible for it to overlap two rows. The *icon* for the cursor, however, spans several rows and may or may not be rendered to point to the actual point that the cursor is at.

comment:2 in reply to:  1 Changed 4 years ago by smoitra

Replying to scott.gonzalez:

The cursor is actually a single point, so it's impossible for it to overlap two rows. The *icon* for the cursor, however, spans several rows and may or may not be rendered to point to the actual point that the cursor is at.

Thanks for the comment. We rechecked once again and the same use-case was working in earlier versions. We understand that the cursor is a single point - the issue is which point is referred to in a cursor icon. We tested with 2 cusror icons in Windows- default and crosshair. For the default cusror icon- the expectation is that the topmost tip of the arrow should be the single point of the cursor - but the actual behaviour is not that. The point is somehwere below the centre of gravity of the cursor. Similarly, for crosshair cursor - the expectation is that the intersecting point is the cursor point. But once again - the cursor point seems to be towards the lower side.

Kindly let us know - if it is feasible to pin point the single point to the user expectation.

comment:3 Changed 4 years ago by Scott González

The only think I can think of would be subpixel rounding. Is the position you're getting different from the position reported by the event you're passing?

Note: See TracTickets for help on using tickets.