Skip to content

Additional usage guidance for IDL attribute types (such as DOMString?) #11078

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
Open
rahimabdi opened this issue Feb 26, 2025 · 1 comment · May be fixed by #11153
Open

Additional usage guidance for IDL attribute types (such as DOMString?) #11078

rahimabdi opened this issue Feb 26, 2025 · 1 comment · May be fixed by #11153
Assignees
@rahimabdi

Comments

@rahimabdi
Copy link
Contributor

What is the issue with the HTML Standard?

The HTML spec may benefit from normative guidance on using the most appropriate type for IDL attributes.

For example, as part of a recent ARIA-motivated update to the DOMString? getter, @domenic called out that DOMString? may need to be discouraged for non-enumerated attributes. @annevk also agreed that general clarity on attribute design would be beneficial, so this issue would not be limited to DOMString? usage recommendations.
This was referenced Feb 26, 2025
Closed
Closed
@rahimabdi rahimabdi self-assigned this Mar 1, 2025
@rahimabdi rahimabdi linked a pull request Mar 23, 2025 that will close this issue
Open
@rahimabdi
Copy link
Contributor Author

@domenic @annevk This one is ready for review: #11153.

I'm getting a strange PR run error with my ReSpec link reference to classList; DOM spec shows that it should be linked via #dom-element-classlist but it doesn't appear to work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rahimabdi rahimabdi

Labels
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add guidance on IDL attribute design rahimabdi/html
1 participant
@rahimabdi