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
User selection #81
Comments
the css_hacks option disables the css properties, but it may cause problems when dragging, holding. the user-select property disables the browser functionality, like you noticed :-) |
If anyone stumbles upon this issue now, as I have, this option has been renamed to "stop_browser_behavior". You can disable this behavior by setting the option to false. |
I can't get this to work — I've done this: var hammertimetap = Hammer(content, { where "content" is a reference to a div-element. It sort-of works, although I can still not select text. Any ideas on where I'm going wrong? Thanx. |
Aaaah, didn't see that — thanx a lot, that works! |
If anybody stumbles across this issue like I did, note the the option name has changed again. It's now called
|
Its very weird, even if cssProps is blank it enables userSelect. Am I missing anything?
|
place this before the initialization of your hammer object |
@jpatel3 It only overwrites specified cssProps, so an empty cssProp will result in the defaults being used. This worked for me:
@Bargs You should probably set it to something of |
See hammerjs/hammer.js#81 for more information.
In case someone is still having/want to overcome this issue. The following excerpt is from hammerjs tips section. And it works too.
Or |
Hey there,
thanks for developing the framework. I just have a question that might already have been answered. If so, please let me know and excuse me.
Hammer.js currently serves this -webkit-user-select: none on the body tag and also the touch-derivate. Is this necessary and why is it?
The problem is (as all of you can imagine) that user cannot select text anymore which for me is a real blocker issue. Can I somehow prevent this behavior?
Thanks for clarification!
-Anselm
The text was updated successfully, but these errors were encountered: