Skip to content

Update to Parley 2025-03-25. #941

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

Merged
merged 1 commit into from
Apr 29, 2025
Merged

Conversation

xStrom
Copy link
Member

@xStrom xStrom commented Apr 29, 2025

With #936 stalling but Matt wanting AccessKit changes I decided to split out parts of #936 into this PR. This brings in Parley from March 25th, 2025 and that gets us the AccessKit update.

Copy link
Member

@DJMcNab DJMcNab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems reasonable

@xStrom xStrom added this pull request to the merge queue Apr 29, 2025
Merged via the queue into linebender:main with commit 17aea51 Apr 29, 2025
35 of 36 checks passed
@xStrom xStrom deleted the parley-ak-update branch April 29, 2025 17:07
accesskit = "0.17.0"
accesskit_winit = "0.23.0"
accesskit = "0.18.0"
accesskit_winit = "0.24.0"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This update means that we no longer support NativeActivity, an unfortunate regression. We panic at this code.
https://github.com/AccessKit/accesskit/blob/10f4bd1344b98ebb2baf969e62afdd767f5ff1d1/platforms/winit/src/platform_impl/android.rs#L31-L39. It looks like the non-support for NativeActivity is intentional here.

cc @mwcampbell what do you suggest doing in this case? Is there a no-op AccessKit winit backend we can use, or is the only solution to conditionally compile out the accessibility support on Android if we want to support Native Activity?

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.

2 participants