autocorrect property #24249
Merged
autocorrect property #24249
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
github-actions
bot
added
data:api
hamishwillee
force-pushed
the
autocorrect_html
branch
from
26b39be to
f30d14a
Compare
What is the behavior of autocorrect on passwords? |
caugner
requested changes
Oct 2, 2024
@caugner The spec states that autocorrect should not work on passwords. However the safari implementation does act on passwords if this feature is enabled on the input. Note that apparently Safari are moving to a compliant implementation. BTW, thank you for all these reviews. The BCD team are clearly hammered because this has been waiting a while. |
caugner
approved these changes
Oct 7, 2024
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.
The global autocorrect property was previously Safari-only, but has now become part of the HTML spec. This adds the element and API to BCD.
Testing on browsertack shows that the property starts to appear on HTMLElement from Safari 14.1. Also that contrary to the spec:
There might be other things, but it does seem to otherwise match the spec. I have added as partial implementation.
Part of mdn/content#35593
Fixes #22704