You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 5, 2024. It is now read-only.
In the setup command, it passes an option hideTimeout. This option should be hideDelay. The test passes because there is an auto-hide on null hideDelay options.
This test would fail if the $timeout.flush() was changed to $timeout.flush(1234).
The text was updated successfully, but these errors were encountered:
adamweeks
added a commit
to adamweeks/material
that referenced
this issue
May 5, 2015
In the `should hide after duration` unit test, an option value is provided to the parameter
`hideTimeout`. This option is not valid and should be `hideDelay`. The test passes
because the toast will default to hide after 3000 anyway.
angular#2728
In the `should hide after duration` unit test, an option value is provided to the parameter
`hideTimeout`. This option is not valid and should be `hideDelay`. The test passes
because the toast will default to hide after 3000 anyway.
Fixes#2728. Closes#2729.
In the
toast.spec.js
file, there is a unit test for'should hide after duration'
that gives a false positive:https://github.com/angular/material/blob/master/src/components/toast/toast.spec.js#L151
In the
setup
command, it passes an optionhideTimeout
. This option should behideDelay
. The test passes because there is an auto-hide on nullhideDelay
options.This test would fail if the
$timeout.flush()
was changed to$timeout.flush(1234)
.The text was updated successfully, but these errors were encountered: