UX/UI: Amélioration des champs de saisie de dates #5504
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The previous version was relying on `UIEvent.which` to identify the key being pressed, which is deprecated. https://developer.mozilla.org/en-US/docs/Web/API/UIEvent/which Also, typing out `01/` would result in `01//`, the first slash being inserted automatically and the second `/` being added when the user hits the `/` key.
francoisfreitag
added
the
no-changelog
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤔 Pourquoi ?
L’implémentation précédente était basée sur
UIEvent.which, qui est dépréciée : https://developer.mozilla.org/en-US/docs/Web/API/UIEvent/whichCorriger un bug qui m’énerve depuis 2 ans, taper
01/écrit01//dans le champ.