Repository navigation
H5 Delay on dropping elements on latest Chrome MacOS Big Sur #1541
Description
Subject of the issue
Disturbing delay on dropping grid item after they were dragged around
Your environment
- Gridstack.js version: 3.1.2 with HTML5
- Google Chrome Version 87.0.4280.88 (Official Build) (arm64)
Steps to reproduce
Visit homepage of library and drag any grid-item of any example.
Expected behavior
No delay on dropping grid-items after they were dragged around
Actual behavior
Delays 1-2 seconds on dropping grid-items after they were dragged around
Activity
[-]Delay on dropping elements on Chrome MacOS Big Sur[/-][+]Delay on dropping elements on latest Chrome MacOS Big Sur[/+]adumesny commentedon Dec 20, 2020
what browser is that for and do you see the same slowdown in other browsers (which I don't see on chrome/Win10)
[-]Delay on dropping elements on latest Chrome MacOS Big Sur[/-][+]H5 Delay on dropping elements on latest Chrome MacOS Big Sur[/+]kevinlandsberg commentedon Dec 20, 2020
Hi @adumesny ,
this slowdown happened to me on Googles Chrome and Firefox on MacOS Big Sur latest version, also latest versions of both browsers. In Safari gridstack does not seem to work anyway...
I cannot reproduce these issues on Windows on any browser also...
[-]H5 Delay on dropping elements on latest Chrome MacOS Big Sur[/-][+]H5 Hard delay on dropping elements on latest Chrome MacOS Big Sur[/+][-]H5 Hard delay on dropping elements on latest Chrome MacOS Big Sur[/-][+]H5 Delay on dropping elements on latest Chrome MacOS Big Sur[/+]adumesny commentedon Jan 4, 2021
no longer seeing the issue with Chrome and 3.1.3-dev build (appears fixed), BUT still seeing on Safari! (it animates back to original location (if I force a clone copy I can see old+new), then to new location - hence the 300msec delay before animating to dropped location.
kevinlandsberg commentedon Jan 6, 2021
@adumesny , correct. Still seeing delays on dropping elements.
H5 Safari fix delay when dropping
H5 Safari fix delay when dropping
adumesny commentedon Jan 9, 2021
fixed in next 3.1.4 release