Add matches and closest functions to Web.DOM.Element.
#4
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
utkarshkukreti
force-pushed
the
element-matches-and-closest
branch
from
89f9975 to
6e072d7
Compare
|
Hey, thanks for the PR and sorry about the slow reply! I was intending on sticking to the W3C HTML 5 specs for these libraries rather than the living standard - it's a bit conservative for the most part, but it hopefully means there's less of a chance of cross-browser compatibility issues with these libraries. |
|
Ah ok. I'll just put these in a js file in my project. |
sigma-andex
pushed a commit
to working-group-purescript-es/purescript-web-dom
that referenced
this pull request
Apr 14, 2022
…escript-web#4) Add `HTMLDocument.currentScript`
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.
Hi @garyb, these functions are documented here:
closestis marked as "experimental" but it's present in the DOM Living Standard.I'm not sure what your policy is on functions not supported by all browsers but I needed this in something I'm working on so I thought I'd send a PR for you to review.