Ticket #4140 (closed bug: wontfix)

Opened 6 years ago

Last modified 5 years ago

Snap to Grid issues with browser zoom

Reported by: Jay Owned by:
Priority: major Milestone: 1.8
Component: ui.draggable Version: 1.6rc6
Keywords: Cc:
Blocking: Blocked by:

Description

There is an issue with snapping to grid when the browser uses its internal zoom functionality. The snapping appears to be snapping to the correct position at first then shifts right by approximately 5 pixels.

This can be replicated on  http://jqueryui.com/demos/draggable/#snap-to in Internet Explorer 7 and by holding the CTRL key and scrolling the mouse.

I understand it may be very difficult to detect the fact that the browser is zoomed, but the majority of novice users may be zoomed at 125% without even realising it.

Change History

comment:1 Changed 6 years ago by Jay

I've also found another bug reported which states that this shift occurs in Internet Explorer and therefore I may not be noticing it with snapping enabled. However when zoomed the snap is incorrect and still snaps to the specified px size rather than the px * zoom.

Also when the browser is zoomed my draggables seem to leave their content behind, for example the div will move around freely but the text content will stay in its original position and only move on the Y axis.

comment:2 Changed 6 years ago by Jay

During zoom in Firefox, the innerWidth property appears to report a different value. The div element is 100% width in css. However this does not occur in Internet Explorer.

comment:3 Changed 6 years ago by Jay

I am using the grid property and not the snap to element property.

comment:4 Changed 6 years ago by scott.gonzalez

  • Milestone changed from TBD to 1.6

comment:5 Changed 5 years ago by rdworth

  • Milestone changed from 1.7 to 1.8

comment:6 Changed 5 years ago by paul

  • Status changed from new to closed
  • Resolution set to wontfix

Unfortunately it is impossible to my knowledge to reliably detect the page zoom and its value in any browser, so I have to close this ticket for now. If you find a way to detect it that doesn't cause significant overhead, please reopen.

Note: See TracTickets for help on using tickets.