Publish Next Version #452
Merged
Publish Next Version #452
Conversation
This file contains 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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
github-actions
bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
7194640
to
b7070ec
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
b7070ec
to
1e4fe28
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
pleasantest@2.0.0
Major Changes
#345
847cbd8Thanks @calebeby! - Normalize whitespace ingetAccessibilityTreeNow anytime there is contiguous whitespace in text strings it is collapsed into a single space. This matches the behavior of browser accessibility trees.
This is a breaking change because it changes the
getAccessibilityTreeoutput, and may break your snapshots. Update your snapshots with Jest and review the changes.#446
1eaa648Thanks @calebeby! - Use document.title as fallback implicit accessible name for html root element in accessibility tree snapshots#445
5fa4103Thanks @calebeby! - Add heading levels togetAccessibilityTree. The heading levels are computed from the corresponding element number in<h1>-<h6>, or from thearia-levelrole.In the accessibility tree snapshot, it looks like this:
This is a breaking change because it will cause existing accessibility tree snapshots to fail which contain headings. Update the snapshots to make them pass again.
#451
eb364ccThanks @calebeby! - Addedaria-expandedsupport togetAccessibilityTreeand fix handling for<details>/<summary>Now, elements which have the
aria-expandedattribute will represent the state of that attribute in accessibility tree snapshots.<details>/<summary>elements will represent their expanded state in the tree as well.Also, for collapsed
<details>/<summary>elements, the hidden content is now hidden in the accessibility tree, to match screen reader behavior.#248
abe22a6Thanks @gerardo-rodriguez! - Enforce minimum target size when callinguser.click(), per WCAG Success Criterion 2.5.5 Target Size guideline.Minor Changes
cf3ad32Thanks @renovate! - Update puppeteer to 13.5.2