[Bug]: Auto completion of expiration date to quick / sets wrong date
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
When creating a link or email share and trying to set the expiration date manually via keyboard at the point typing the year you have to be very fast, otherwise a wrong date will be automatically completed after two seconds.
Imagine I want to have an expiration date of 01.06.2024 the auto completion would set the date 01.06.1920.
Steps to reproduce
- Create a link or email share.
- Try to set the expiration date 01.06.2024 and wait 2 seconds while typing 20.
Expected behavior
The time span for entering the date should be a little bit longer that the user has more time to insert the date.
If a date is automatically completed it should be a realistic one, e.g. if the user enters 24 he wants 2024 and not 1924.
Nextcloud Server version
27
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no file, test, or entry point. Start by reproducing the expiration-date input flow for a link or email share, using the stated steps and Nextcloud Server version 27. Done means manual entry allows more time and a partial year such as 24 is completed as 2024 rather than 1924.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100