Credit Card Entry - Cannot Remove Date Field
I checked if this (admittedly minor but annoying) issue had been fixed with the new release. It can be tracked back (at least) to 2016 and I re-raised the issue in June 2023. Apparently "listening" to customers does not imply reacting.
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided
Comments
-
The issue is currently open and is on the teams radar. To be clear this affects the desktop application. You should be able to access 1Password.com and edit the date as needed. I was able to do this with a test entry. I've added your report to our tracker.
ref: dev/core/core#15945
0 -
This same problem occurs with the Android app and Windows app.
The workaround of using the browser does not work on a Credit Card entry anymore because there is no X to click on the expiry date entry to remove it. It's one of the standard credit card fields. (If you add a new date field, the new entry has an X and can be deleted.)
0 -
I'm sorry that you're also running into the issue, I've shared your report with the team. Out of curiosity, why are you trying to remove the date entirely rather than replacing it with a new date? Wouldn't you want to include the Expiry and Valid From dates in the Credit Card item in case you need that information?
The workaround of using the browser does not work on a Credit Card entry anymore
The workaround that my colleague Tommy mentioned applied to the old version of the 1Password.com web app. We recently released a new version of the web app that is more consistent with the desktop app but it inherited the same date issue as a result.
-Dave
ref: dev/core/core#15945
0 -
It's really the valid from field because my card doesn't have that date. Unfortunately, I had put the expiration date there, and now can't clear the field. So, I was trying to delete it all together.
0 -
Thank you for clarifying. For the time being, creating a new Credit Card item and copying your data over to the new item would be the best workaround.
Hopefully this can be resolved in a future update soon.
-Dave
0
