Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WPS: Date or time widget reset after typing in values is unexpected (chrome) #6896

Open
sppigot opened this issue Sep 18, 2023 · 3 comments · May be fixed by #7021 or #7026
Open

WPS: Date or time widget reset after typing in values is unexpected (chrome) #6896

sppigot opened this issue Sep 18, 2023 · 3 comments · May be fixed by #7021 or #7026
Assignees

Comments

@sppigot
Copy link
Contributor

sppigot commented Sep 18, 2023

When manually typing in either a date to the date time widgets in chrome (116.0.5845.188 or 117.0.5938.89 but this has been around in earlier versions too) the browser will reset and lose the value in the time widget. The opposite also happens in that, if you type in a time in the time widget, then your previously entered date will be reset and lost. e.g.

Typed in a date to the date widget:

typing-in-date

Then typing in a time to the time widget and the date widget gets reset: and my previously entered date is lost:

typing-in-a-time

This is a bit frustrating for power users who don't use the click helpers.

Doesn't seem to happen with firefox.

@AnaBelgun
Copy link
Member

Update 5 Jan

  • patching it as a React 18 tss component (convert to a class component as a transitionary step) or refactoring? Brendon will look into properly refactoring because it's a popular component/used in many places

@sixlighthouses
Copy link
Contributor

Draft PR #7021

@nf-s nf-s linked a pull request Jan 10, 2024 that will close this issue
3 tasks
@sixlighthouses sixlighthouses linked a pull request Jan 11, 2024 that will close this issue
3 tasks
@sixlighthouses
Copy link
Contributor

requires some rework, with reference to PR comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants