-
Notifications
You must be signed in to change notification settings - Fork 3.4k
md-tooltip eats the button click on mobile #6792
Comments
is there a codepen avail? |
Don't have a codepen set up (for some reason I've been having problems with On Wed, Jan 20, 2016 at 7:27 PM, 0101adm notifications@github.com wrote:
|
You have to be on the actual mobile device. Simulating a touch screen on On Wed, Jan 20, 2016 at 7:45 PM, 0101adm notifications@github.com wrote:
|
it could be a conflict from another lib. |
I am also having this same issue. It is not a conflict from another library. The tooltip is displayed on first click, and the click action is done on the second click. Not very effective. |
I can confirm this issue as well. But for me it works correctly on chrome running on Android but not on iOS (both safari and chrome). To me it seems that single tap on ios is treated the same as long one on android. |
I also had this issue and worked around it by adding |
@schmkr thanks for the fix! |
+1 and also a thanks to @schmkr for the fix. Unfortunately that doesn't work in one case. I have a button with a tooltip, and when you click that button it pops up a dialog. When you add in the md-delay attribute (no matter the setting, even 0) it fixes the need to double tap to actually press the button, but now it just pops up the tooltip on top of the dialog after it opens. So this doesn't really solve the problem either. |
@rfuhrer the following will solve your problem (if the dialog is not using any special body.md-dialog-is-showing md-tooltip {
display: none; // hide the tooltip when the dialog is open due to bug on mobile devices
} @ everyone else, yes, this is an issue. Tested on mobile safari with 1.1.0-rc.5, and adding |
If an md-button has a md-tooltip inside it, and you click on the button, the tooltip shows up, but the button doesn't receive a click event. A second click is necessary.
The text was updated successfully, but these errors were encountered: