Skip to content

Add new category for typeable form controls with normalization #1910

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Holo-xy
Copy link

@Holo-xy Holo-xy commented Jul 6, 2025

There looks to be a popular demand for normalized date and datetime-local as seen in 1470 and 42322342.
This introduces a new category to make the expected behavior explicit.


Preview | Diff

@Holo-xy
Copy link
Author

Holo-xy commented Jul 6, 2025

P.S. I wasn't sure if I should group the common logic of non-typable and typeable or not.

A <dfn>typeable form control with normalization</dfn>
is an [^input^] element
whose [^input/type^] attribute state
requires that user-provided values be normalized before being assigned to the element's value attribute.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should probably be more specific and define how exactly the input values should be normalized for date types. Also I wonder if it could be made optional because I imagine some existing clients would want to keep the current non-normalized behavior.

cc @whimboo @jgraham @sadym-chromium

@OrKoN OrKoN requested review from whimboo and sadym-chromium July 30, 2025 06:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants