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

AccessKit node bounds are never clipped #7382

Open
DataTriny opened this issue Jan 15, 2025 · 0 comments
Open

AccessKit node bounds are never clipped #7382

DataTriny opened this issue Jan 15, 2025 · 0 comments
Labels
a:accessibility Support for assistive technologies (mS,bT) bug Something isn't working need triaging Issue that the owner of the area still need to triage

Comments

@DataTriny
Copy link
Contributor

Bug Description

When an element contained in a scroll view is only partially visible, its AccessKit Node::bounds should be set accordingly.

To reproduce

  • Run the crud example
  • Scroll the list view a bit so that the first item is partially hidden
  • Observe with an accessibility inspector that the first item's bounding box goes outside of the item's parent bounding box.

Reproducible Code (if applicable)

Unmodified crud example exhibits the bug.

Environment Details

  • Slint Version: master branch
  • Platform/OS: Windows 11
  • Programming Language: Rust
  • Backend/Renderer: winit

Product Impact

No response

@DataTriny DataTriny added bug Something isn't working need triaging Issue that the owner of the area still need to triage labels Jan 15, 2025
@ogoffart ogoffart added the a:accessibility Support for assistive technologies (mS,bT) label Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:accessibility Support for assistive technologies (mS,bT) bug Something isn't working need triaging Issue that the owner of the area still need to triage
Projects
None yet
Development

No branches or pull requests

2 participants