Fix: A potential TypeError due to shadowed contains in ElementObserve #842
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.
This PR fixes a potential
TypeError: this.element.contains is not a functionerror inElementObserver. This error can occur if a child element shadows the nativecontainsmethod.To resolve this, the PR replaces
this.element.contains(element)withHTMLElement.prototype.contains.call(this.element, element)in theelementIsActivemethod. This ensures that the nativecontainsmethod is always called, regardless of any naming conflicts.For example, consider the following HTML:
In this case, the
<input name="contains">shadows the nativecontainsmethod on the<form>element, leading to aTypeError: this.element.contains is not a functionerror at runtime.