Firefox appears to limit it to a max depth of 200.

Deleted: layout_tree.html 463 bytes

layout_tree.html 463 bytes View Download

Should we implement a depth limit for NG? 

We should seriously consider it - 

Verified that FF == 200, I tried with Edge and on my VM they capped out at ~500, they probably don't have a firm limit and might be stack heavy.

We are initially going to be very stack heavy so we'll probably have a lower limit than we do today - we may want to bring this up at the next CSSWG and try to standardize on a reasonable upper limit. 

Additional context with NG we'll be able to produce a fragment tree which we can use which will keep the page still interactive if we want even if folks go over this limit. Alternatively we may want to just jump somewhere sane and crash.

 Issue 760796  has been merged into this issue.

Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.

 Issue 773574  has been merged into this issue.

ClusterFuzz testcase 5614405902663680 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

 Issue 795739  has been merged into this issue.

 Issue 797537  has been merged into this issue.

 Issue 804089  has been merged into this issue.

 Issue 827877  has been merged into this issue.

 Issue 842889  has been merged into this issue.

 Issue 855837  has been merged into this issue.

 Issue 857184  has been merged into this issue.

 Issue 879946  has been merged into this issue.

 Issue 888605  has been merged into this issue.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/27d732d9364e1f139dafdbacc813318b5a9a852f (Reland Devirtualize LayoutBoxModelObject logical orientation border/margin/padding accessors).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.