-
Notifications
You must be signed in to change notification settings - Fork 12
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.
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
Expose ariaAllowedAttributes on ARIA Element #1721
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 4701841 The changes in this PR will be included in the next version bump. This PR includes changesets to release 78 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
b9ce81c
to
d681986
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great. A few nitpicking code style comments.
No. YAGNI. We'll move it when we need it… |
The Integrate workflows fails because it detects change in the API (the new method) that has not been registered in the docs. You can extract the new API by using |
!pr extract |
Move the logic from 'r18/rule.ts' into the alfa-aria package.
d681986
to
e7d8b49
Compare
Co-authored-by: Jean-Yves Moyen <jym@siteimprove.com>
I ran it locally and force pushed approximately when you were writing that comment, I think (hadn't noticed you had started reviewing, so I thought I could sneak it in) |
e8b53d7
to
4bcaf87
Compare
The logic is moved from R18 implementation and made public.
Should we also have a
prohibitedAttributes()
function on the Element type, for symmetry?