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

fix click event for mobile devices and old browser #441

Merged
merged 4 commits into from
Jun 27, 2015
Merged

fix click event for mobile devices and old browser #441

merged 4 commits into from
Jun 27, 2015

Conversation

ChiefORZ
Copy link
Contributor

fix for #411 #250 and #436
as well as #387
and #146 #393

added forcePolyfill option.

  • forcePolyfill is made to make cross-browser testing more easy.
  • forcePolyfill provides a reliable, consistent cross-browser Solution for
    Sortable.
  • forcePolyfill gives us the possibility to change the way "dragged items"
    lok like.

added forcePolyfill option.
forcePolyfill is made to make cross-browser testing more easy.
forcePolyfill provides a reliable, consistent cross-browser Solution for
Sortable.
forcePolyfill gives us the possibility to change the way "dragged items"
lok like.
@ChiefORZ
Copy link
Contributor Author

i don't know anything about grunt, i'm sorry.

would be a waste of time if i tried to make something happen with it ;)

modified the private _onMove prototype, so it calls events on it's
source Element like it's sibling function _dispatchEvent
added the handleMove, which listens to the onMove events to the react
mixin
@ChiefORZ
Copy link
Contributor Author

also fixed my own issue #407

@ChiefORZ
Copy link
Contributor Author

I should point out: Line 470 is absolutely optional... i just made it append to the Document Body because it fixed the Bug issued in #387.

We can alternatively append a different className to the polyfilled/cloned Element.

@denyss86study
Copy link

Thanks a LOT!! Your commit fixed issues we have with Sortable on both Android and iPhone. I hope it will be merged into the master branch.

wasn't merging all necessary stuff. now it should be fully functional
@@ -466,12 +471,28 @@
_css(ghostEl, 'position', 'fixed');
_css(ghostEl, 'zIndex', '100000');

rootEl.appendChild(ghostEl);
document.body.appendChild(ghostEl);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ghostEl should be into rootEl, otherwise we will get the wrong display using CSS:

.root-block .dragged-item {
    color: red;
}

removed the default behaviour to append the cloned Element to the body.
now the cloned Element gets added in the same parent, with the addition
of the class defined in options.fallbackClass.
added the possibility to change the fallback class.
added the possibility to decide wheter the fallback should be cloned
into the same parent or to the document's body.
@RubaXa
Copy link
Collaborator

RubaXa commented Jun 27, 2015

Cool! Thanks you.

RubaXa added a commit that referenced this pull request Jun 27, 2015
fix click event for mobile devices and old browser
@RubaXa RubaXa merged commit 71f4362 into SortableJS:dev Jun 27, 2015
@ChiefORZ
Copy link
Contributor Author

Please don't forget, that i haven't minified it... You need to run grunt, if you don't mind.

Thanks!

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

Successfully merging this pull request may close these issues.

3 participants