Update dom-input-range to fix DOMException errors
#56
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
iansan5653
changed the title
dom-input-nodedom-input-node to fix DOMException errors
iansan5653
changed the title
dom-input-node to fix DOMException errorsdom-input-range to fix DOMException errors
iansan5653
force-pushed
the
update-dom-input-node
branch
from
5187182 to
02dec0d
Compare
keithamus
approved these changes
May 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Updates
dom-input-rangeto1.1.6to fixDOMExceptionerrors. The dependency was throwing exceptions when the custom element was registered a second time, which would happen on soft navigations. This was resolved in iansan5653/dom-input-range#4