-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Query: Try adding infinite scroll loading #56987
Conversation
Warning: Type of PR label mismatch To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.
Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task. |
Size Change: +610 B (0%) Total Size: 1.71 MB
ℹ️ View Unchanged
|
Flaky tests detected in 2a39741. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7195816355
|
Hey @gziolo, Really need to watch accessibility with an approach like this. Any type of load more action needs to very carefully manage focus and communicate clearly to assistive technology. I would much prefer we keep the pagination approach. Please get reviews from the Accessibility Team if you get this in a place ready for reviews. Thanks. |
Hey @alexstine, absolutely 🙂 This was just a quick proof of concept to test how the |
@alexstine, it feels so great having your comment on the early prototype for one of the potential features we could add to the Query block or Comments block. I wanted to echo what Luis said. There is no immediate plan to continue working on it, but once we get back to it, we definitely will reach out to the Accessibility team for support in shaping how it all works. Many classic themes use the infinite scroll feature, so it would be great to add it for feature parity, but we have this unique opportunity to make it accessible for everyone by leveraging the Interactivity API.
The way the Query block works without the page reload covers the communication part when using assistive technology. It announces that the page has changed using the same mechanism as in the block editor. We definitely could reuse that for infinite scroll. Do you have some initial thoughts on how we could go about the focus management? This is what I was thinking so far. If we put the |
@gziolo I think placing focus on the newly loaded post is okay. |
I opened #59943 to track it. I'm closing the prototype for now as I don't plan to work on it in the upcoming weeks. |
What?
See #59943.
Many classic themes use the infinite scroll feature, so it would be great to add it for feature parity to core blocks. We have this unique opportunity to make it accessible for everyone by leveraging the Interactivity API. This PR explores what is necessary to add the feature to the Query Loop block.
This is an early prototype. There is no immediate plan to land it in the Gutenberg plugin. However, it would be great to gather some initial feedback about the requirements for making it accessible.
Why?
How?
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast
Infinite.scroll.mp4