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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
dom-accessibility-api@0.4.4
Patch Changes
e79f620
#208 Thanks @eps1lon! - Add support for node 142c6a23b
#200 Thanks @eps1lon! - Addmodule
field737dfae
#234 Thanks @willamzv! - Consider<legend>
for the name of its<fieldset>
element.Computing the name for this fieldset would've returned an empty string previously. It now correctly computes
my fieldset
following the accessible name computation forfieldset
elements969da7d
#240 Thanks @eps1lon! - Reduce over-transpilationSwitched from
for-of
to.forEach
or a basicfor
looparray.push(...otherArray)
topush.apply(array, otherArray)
This removed a bunch of babel junk that wasn't needed.
d578329
#248 Thanks @eps1lon! - Consider<caption>
for the name of its<table>
element.Computing the name for this table would've returned an empty string previously. It now correctly computes
my table
following the accessible name computation fortable
elementsf1b2bd0
#237 Thanks @eps1lon! - Use nodeType and tagName for element type checks