Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with 'transform: translate3d()' for .sortable-drag in Firefox #1423

Closed
mckey opened this issue Jan 14, 2019 · 6 comments
Closed

Issue with 'transform: translate3d()' for .sortable-drag in Firefox #1423

mckey opened this issue Jan 14, 2019 · 6 comments

Comments

@mckey
Copy link

mckey commented Jan 14, 2019

Problem:

Plugin (1.7 and 1.8.rc1) does not consider 'transform: translate3d()' css property for .sortable-drag element in latest firefox (v64).

JSBin/JSFiddle demonstrating the problem:

https://jsbin.com/cuyutitepe/1/edit?html,css,js,output

@owen-m1
Copy link
Member

owen-m1 commented Jan 15, 2019

@mckey 1.8.0 is released with this issue solved

@owen-m1 owen-m1 closed this as completed Jan 15, 2019
@mckey
Copy link
Author

mckey commented Jan 15, 2019

Don't see any difference. The issue is still present.

@owen-m1
Copy link
Member

owen-m1 commented Jan 15, 2019

@mckey It works for me on the latest firefox... if you were using githack it would have taken some time to update to the latest version

@mckey
Copy link
Author

mckey commented Jan 15, 2019

@owen-m1 in jsbin from my first comment looks like the latest version - https://raw.githack.com/SortableJS/Sortable/master/Sortable.js

In my project I use this library as separate file and in my firefox 64.0.2 (64 bit) issue is still present.

@owen-m1
Copy link
Member

owen-m1 commented Jan 15, 2019

@mckey Oh I see your issue. The issue I fixed was the "sortable-drag" element being out of place when the translate was applied and forceFallback was set to true. If you have forceFallback: false (as your example does), then the "sortable-drag" element is being created and positioned by the browser. This is most definitely an issue with firefox.

For now, you can fix it by setting forceFallback: !!navigator.userAgent.match(/firefox/i)

@mckey
Copy link
Author

mckey commented Jan 15, 2019

Thank you, @owen-m1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants