New pages: HTMLxElement.setCustomValidity() #35948
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
github-actions
bot
added
Content:WebAPI
Josh-Cena
approved these changes
Sep 19, 2024
| ### Parameters | ||
|
|
||
| - `string` | ||
| - : The string containing the error message. |
There was a problem hiding this comment.
Suggested change
| - : The string containing the error message. | |
| - : The string containing the error message. The empty string removes any custom validity errors. |
|
|
||
| {{ APIRef("HTML DOM") }} | ||
|
|
||
| The **`setCustomValidity()`** method of the {{DOMxRef("HTMLButtonElement")}} interface sets the custom validity message for the {{htmlelement("button")}} element to the specified message. Use the empty string to indicate that the element does _not_ have a custom validity error. |
There was a problem hiding this comment.
Suggested change
| The **`setCustomValidity()`** method of the {{DOMxRef("HTMLButtonElement")}} interface sets the custom validity message for the {{htmlelement("button")}} element to the specified message. Use the empty string to indicate that the element does _not_ have a custom validity error. | |
| The **`setCustomValidity()`** method of the {{DOMxRef("HTMLButtonElement")}} interface sets the custom validity message for the {{htmlelement("button")}} element. Use the empty string to indicate that the element does _not_ have a custom validity error. |
Josh-Cena
reviewed
Sep 19, 2024
|
|
||
| {{ APIRef("HTML DOM") }} | ||
|
|
||
| The **`setCustomValidity()`** method of the {{DOMxRef("HTMLFieldSetElement")}} interface sets the custom validity message for the {{htmlelement("fieldset")}} element to the specified message. Use the empty string to indicate that the element does _not_ have a custom validity error. |
There was a problem hiding this comment.
Mention that fieldset/output are not validation targets and therefore the message won't actually be displayed when calling reportValidity (but will be reported by the validity object)?
|
Also, I suggest porting whatever template we used for these few pages to the existing |
fiji-flo
pushed a commit
that referenced
this pull request
Oct 2, 2024
* New pages: HTMLxElement.setCustomValidity() * edits based on review
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.
part of #35544