-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
docs(animations): increase wait time for status-slider animation #35089
docs(animations): increase wait time for status-slider animation #35089
Conversation
Setting @IgorMinar as reviewer as @matsko is out today |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm except for the commit message which should have been test(animations): ...
"docs:" is for docs only content - https://github.com/angular/angular/blob/master/CONTRIBUTING.md#type
as discussed in person, we could argue that this is a primarily "docs" change. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Because the animation completes in 2000ms, and browser.wait checks every 100ms, there can be a race condition of if the final state has actually been reached to read the color. By moving to 2101ms, we ensure that we cheack after the 2000ms of the animation has completed.
b15a4c5
to
ef4c83e
Compare
) Because the animation completes in 2000ms, and browser.wait checks every 100ms, there can be a race condition of if the final state has actually been reached to read the color. By moving to 2101ms, we ensure that we cheack after the 2000ms of the animation has completed. PR Close #35089
…ular#35089) Because the animation completes in 2000ms, and browser.wait checks every 100ms, there can be a race condition of if the final state has actually been reached to read the color. By moving to 2101ms, we ensure that we cheack after the 2000ms of the animation has completed. PR Close angular#35089
…ular#35089) Because the animation completes in 2000ms, and browser.wait checks every 100ms, there can be a race condition of if the final state has actually been reached to read the color. By moving to 2101ms, we ensure that we cheack after the 2000ms of the animation has completed. PR Close angular#35089
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Because the animation completes in 2000ms, and browser.wait checks
every 100ms, there can be a race condition of if the final state has
actually been reached to read the color. By moving to 2101ms, we ensure
that we check after the 2000ms of the animation has completed.
Fixes #35038