Select values lost in snapshots
See original GitHub issueCurrent behavior:
When viewing a snapshot the values of <select>
elements are lost. <input>
element preserve their value fine, however.
This is minor, but it’s happening in my percy tests too and I guess it’s caused by the same thing.
Desired behavior:
<select>
elements should appear in snapshots as they appeared at the time.
Steps to reproduce: (app code and test code)
Repo and steps to replicate in readme: https://github.com/callumacrae/cypress-select-value-issue
Versions
Cypress 3.3.1
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:10 (2 by maintainers)
Top Results From Across the Web
Snapshot Isolation in SQL Server
In this article, we will explore the use of snapshot isolation using row versioning as an alternative to the classic ANSI SQL transaction ......
Read more >Database Snapshots (SQL Server) - Microsoft Learn
A SELECT statement that is executed on a database snapshot must not specify a FILESTREAM column; otherwise, the following error message will be ......
Read more >Restore table snapshots | BigQuery - Google Cloud
In the Restore snapshot pane that appears, enter the Project, Dataset, and Table information for the existing table. Select Overwrite table if it...
Read more >Snapshots | dbt Developer Hub
In dbt, snapshots are select statements, defined within a snapshot block in a .sql file (typically in your snapshots directory).
Read more >Snapshot Manager fails to detect snapshots of VMs (1026380)
Where includeMemory and quiesced variables are Boolean values. Set the value to 1 to enable or 0 to disable the snapshot option.
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
I disagree that this is a minor issue; being able to see the state of the select options in your app is valuable.
However, for users who don’t know that this is a bug in cypress and not a bug in their app, it’s even worse, and can lead to wasted time trying to figure out why the selected values are wrong (which is what happened to me).
That’s what happened to me, too!