This repository was archived by the owner on Sep 5, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
md-tooltip does not default to 400ms delay #1847
Labels
Comments
Also experiencing the directive not defaulting to the 400ms delay. Without the md-delay attribute it displays immediately. Using Chrome Version 41.0.2272.118 (64-bit) |
devversion
added a commit
to devversion/material
that referenced
this issue
Nov 14, 2015
There's no delay described in the Material Spec. |
This issue doesn't mention the material spec. It's an inconsistency with the docs. The latest doc says 300 ms. |
Yep you right, we should update it to 0 |
devversion
added a commit
to devversion/material
that referenced
this issue
Nov 16, 2015
…value (0ms) Closes angular#5728 Fixes angular#1847
devversion
added a commit
to devversion/material
that referenced
this issue
Feb 2, 2016
…value (0ms) Fixes angular#6970 Fixes angular#1847
ErinCoughlan
pushed a commit
to ErinCoughlan/material
that referenced
this issue
Feb 9, 2016
* update docs with default mdDelay == 0 mSecs * update tooltip demo to show md-delay options and affects * remove .md-fab line-height for tooltip fab buttons. Fixes angular#6970. Fixes angular#1847. Closes angular#5748
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The docs here indicate that the default tooltip delay is 400ms: "How many milliseconds to wait to show the tooltip after the user focuses, hovers, or touches the parent. Defaults to 400ms."
The problem is that there does not appear to be any default delay. The tooltips are displayed instantly.
Notice the difference in the code pen. The 'working' tooltips have manually set
md-delay="400"
but the non working tooltips are just using the default. They should be showing the same delay, but you can see that the non working tooltips are much faster (instant).http://codepen.io/Splaktar/pen/emLbQN
Codepen example is using 0.8.3 with Angular 1.3.14.
The text was updated successfully, but these errors were encountered: