Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Missing attributes property access on Element #47

Open
flip111 opened this issue Jan 27, 2022 · 1 comment
Open

Missing attributes property access on Element #47

flip111 opened this issue Jan 27, 2022 · 1 comment
Labels
good first issue First-time contributors who are looking to help should work on these issues. status: accepted This issue is now ready to be implemented via a PR.

Comments

@flip111
Copy link
Contributor

flip111 commented Jan 27, 2022

https://developer.mozilla.org/en-US/docs/Web/API/Element

Element.attributes Read only
Returns a NamedNodeMap object containing the assigned attributes of the corresponding HTML element.

There are some functions to work with attributes here https://pursuit.purescript.org/packages/purescript-web-dom/5.0.0/docs/Web.DOM.Element just sometimes you would like to know which attributes are available before calling getAttribute
@thomashoneyman thomashoneyman added good first issue First-time contributors who are looking to help should work on these issues. status: accepted This issue is now ready to be implemented via a PR. labels Jan 27, 2022
@garyb
Copy link
Member

garyb commented Jan 27, 2022

Please link to the actual standard, as per the issue template!

Here's the IDL: https://dom.spec.whatwg.org/#interface-element

I think it was skipped as we don't have a NamedNodeMap implemented in this library yet either.

@flip111 flip111 mentioned this issue Jan 27, 2022
Closed
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue First-time contributors who are looking to help should work on these issues. status: accepted This issue is now ready to be implemented via a PR.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@garyb @flip111 @thomashoneyman