Sebastian "Sebbie" Silbermann

Not a fan of this since CI is cheap but having devs do additional steps if a middle stackframe fails is expensive. Was there communication that we need to save...

> This may not be too much of an issue right now, but as more people on the team adopt stacked PRs, we'll see people using larger and larger stacks....

* **#69314** 👈 * **#69317** * **#69318** * `canary` This stack of pull requests is managed by Graphite. Learn more about stacking. Join @eps1lon and the rest of your teammates...

Do we have docs where we can explain this functionality? I suspect I need to attach a debugger to get this feature to work?

codemods: https://github.com/vercel/next.js/pull/70064

Sounds to me spec and browser agree. We should compute the name on the referenced elements and use that as the description. Please file a bug against https://github.com/eps1lon/dom-accessibility-api/

* **#71718** 👈 * **#71717** * `canary` This stack of pull requests is managed by Graphite. Learn more about stacking. Join @eps1lon and the rest of your teammates on Graphite

* **#71444** 👈 * **#71653** * `canary` This stack of pull requests is managed by Graphite. Learn more about stacking. Join @eps1lon and the rest of your teammates on Graphite

Flaky test. Merging anyway.

Need to revert since `source-map` uses `Math.random` for quick-sort which triggers warnings with `experimental.dynamicIO`: https://github.com/vercel/next.js/pull/71868