Bug 232176 – Improve performance of nested grids

• Status: NEW
• Component: Layout and Rendering

[Tim Nguyen (:ntim)]

See: http://exponential-layout.glitch.me

From: https://developer.chrome.com/blog/layoutng/

[Radar WebKit Bug Importer]

<rdar://problem/84823492>

[Ulrich Dobiasch]

Safari 16 – still present – 15+ nested grids and the cpu is stalling

[Michael]

Safari 17 – still present – 15+ nested grids and the cpu is stalling

[Mendel Gordon]

See https://web.archive.org/web/20211008182612/https://developer.chrome.com/blog/layoutng/ since the original link is dead 
(In reply to Tim Nguyen (:ntim) from comment #0)
> See: http://exponential-layout.glitch.me
> 
> From: https://developer.chrome.com/blog/layoutng/

[[e-mail]]

Just a comment regarding importance:

Would be nice to see this get higher priority. Grid is used for so many layout problems now, and the developer pain of having to remove all that just for Webkit based browsers is incredible.

[Ahmad Saleem]

I tested this post 276633@main and now this test can be pushed to 100+ without any issue on M1 Pro with 16 GB.

Change progressing this - https://commits.webkit.org/276633@main

@Sammy - should we mark this duplicate of other bug?

[Manuel Rego Casasnovas]

(In reply to Ahmad Saleem from comment #6)
> I tested this post 276633@main and now this test can be pushed to 100+
> without any issue on M1 Pro with 16 GB.
> 
> Change progressing this - https://commits.webkit.org/276633@main
> 
> @Sammy - should we mark this duplicate of other bug?

I can confirm this behavior, without that patch my computer starts to struggle around adding the 15th layer (or earlier). With that patch I've managed to add >150 layers easily.