Number input doesn't increment on .type({uparrow})
See original GitHub issueCurrent behavior:
.type({uparrow})
doesn’t increment the number input.
Additionally I cannot invoke('stepUp')
either.
Desired behavior:
Increments the number input’s value on .type({uparrow})
and invoke('stepUp')
.
Steps to reproduce:
https://github.com/hally9k/cypress-test-tiny
Clone this fork, npm install
and npm start
Versions
macOS 10.13.5 Cypress 3.0.2
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Customized Increment Arrows on Input doesn't work! How to ...
1 Answer 1 · thanks for the suggestion but it doesn't work <input class='quantity' type='number' placeholder='0' [(ngModel)]='item. · Are you sure ...
Read more >Make <input type="number"> respond to arrow keys ... - Bram.us
By default <input type="number"> elements will increment/decrement by its step attribute value when pressing the up/down arrows.
Read more >How to disable arrows from Number input ? - GeeksforGeeks
In this article, we will see how to disable arrows from the Number input. See the Images below, the first image is having...
Read more >Always Show Arrows for Number Input - David Walsh Blog
One native behavior I dislike is that <input type="number" /> elements only show the increment and decrement arrows when the input is ......
Read more >Customize Increment Arrows on Input of Type Number Using ...
It's always tricky to style forms elements and the number element is not properly supported by all browsers yet. So I woul most...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This should be fixed in an upcoming patch release, {uparrow} will be fixed to increment number (not date inputs) , and move cursor on contenteditables and textareas Same fix for {downarrow}
This issue will be closed to further comment as the exact issue here was resolved in Cypress 3.0.3 and tested.
If you’re experiencing a bug similar to this in Cypress, please open a new issue with a fully reproducible example that we can run. There may be a specific edge case with the issue that we need more detail to fix.