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.

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

Update to accesskit 0.18 #294

Merged
merged 1 commit into from
Mar 8, 2025

Conversation

waywardmonkeys
Copy link
Contributor

No description provided.

@waywardmonkeys
Copy link
Contributor Author

I guess this will need a breaking revision published.

@nicoburns
Copy link
Contributor

I guess this will need a breaking revision published.

I really think we should be more liberal with this. If we published a 0.4 version of Parley today with only this version, would anyone be inconvenienced by that? My take is that no, they would not.

Having said that, we could also consider splitting out Parley's accesskit support to live in separate crate, which would alleviate that issue entirely.

@waywardmonkeys
Copy link
Contributor Author

I'm not against a 0.4, but I'll also be suggesting some other things that would be part of a 0.4. I think we'll want to do that 0.4 release sooner rather than later.

@waywardmonkeys waywardmonkeys added this pull request to the merge queue Mar 8, 2025
Merged via the queue into linebender:main with commit eb4b915 Mar 8, 2025
21 checks passed
@waywardmonkeys waywardmonkeys deleted the update-accesskit branch March 8, 2025 09:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants