-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
feat: Implement correct behavior for all input types supporting arrow up (stepUp) and arrow down (stepDown) #29678
base: develop
Are you sure you want to change the base?
Conversation
|
…wn" on supported input types
…} arguments for cy.type() for input[type=date]
# Conflicts: # cli/CHANGELOG.md
…ction that check if "change" and "input" events are triggered
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.
I manually verified this behavior works. It also works correctly when a step
attribute is defined. Thanks for adding this and adding thorough tests around this!
That must be fixed by last commit now |
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.
@thevladisss There’s still a failure in the type test file.
Whoops, I can see, just did not have enough time to check. I will fix in the evening |
@thevladisss These tests are still failing. You can run them locally and verify the type file is passing. |
Actually I did, I wonder why they are failing on CI. Let me troubleshoot it |
I see what the issue is. I actually only tested Chromium browsers. Appears like there is certain specific behavior with Webkit and Firefox for "stepUp" and "stepDown" functions that I would have to account for. I'll do my best to fix it during this week. |
… and "week" for Webkit and Firefox browsers due to missing support
This has been addressed. Now I am facing issue with "sessions.ui.cy.js" and hopefully because my branch is not up-to-date with development. |
@thevladisss It seems the webkit type tests are still failing around the stepUp/stepDown implementation: https://app.circleci.com/pipelines/github/cypress-io/cypress/62710/workflows/7da0f09a-5165-4c47-a7a4-d4e7789f58fa/jobs/2595993 |
I figured that could happen, I just cannot run tests on Webkit locally for some reason... |
I do not want to delay release of this feature, therefore I added check for webkit browser, that for some reason I cannot locally debug. I am acutally struggling to run tests for some reason. I also talked to the teamember in Discord, but that unfortunately did not help me to able to run tests |
@jennifer-shehane I am having issues locally debuggin implementation for Webkit. What would be your best suggestion ? |
For consistency, you could use the existing
|
Additional details
This feature implements natural behavior of inputs that support key down and key up and also support stepper functionality (stepUp and stepDown) according to MDN Docs., affecting
Steps to test
How has the user experience changed?
PR Tasks
cypress-documentation
?type definitions
?