Remove Chrome and Edge specifics from datetime-local behavior #42388
+1
−1
Conversation
This file contains hidden or 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
github-actions
bot
added
Content:HTML
Author
|
Hi @dipikabh, ready for review. PTAL, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
This change updates
datetime-localbehavior notes by removing Chrome and Edge specific descriptions. Chrome now behaves consistently with Firefox for this case.Motivation
The issue was fixed in Chrome M143, aligning
datetime-localbehavior with Firefox. Since Chrome M143 has already reached the Stable release channel, keeping Chrome and Edge specific notes may cause unnecessary confusion for developers.Related issues and pull requests