IssueTracker

The New in Chrome 127 Chrome for Developers announcement says this about keyboard-focusable scroll containers:

From now on scrollers are click-focusable and programmatically-focusable by default.

However, this is only true for 10% of users:

[Chrome is] slowly rolling it out on stable 127. Currently, 10% of users see it. By 128, 100% of users should expect keyboard focusable scrollers to be enabled by default.

I took the blog post at its word, as I (and projects) have been waiting for this feature since its first planned roll out in 118.

I started testing to confirm it worked (it did for me), started updating project documentation and timelines when my tests panned out, and started to socialize it to stakeholders. Then I got reports it did not work, so I had to build tests, recruit people to test, and file a sufficiently detailed bug report so it would not be auto-closed as non-reproducible (since it worked for me).

Please update the post with accurate information, such as the comment from the issue or perhaps:

Starting in 127, scrollers are click-focusable and programmatically-focusable by default for sub-sets of users, ramping up to all users in 128.

To find out that that this won't be available "by default" for 100% of users until maybe 128 means now I have to roll back that some of that effort and prepare to do it all over again. I am confident I am not the only one walking back some efforts (and feeling the loss of political capital as a result).

If my comment sounds like I am frustrated, it's only because I very much am.