diff options
| author | Martin Robinson <mrobinson@igalia.com> | 2025-04-16 17:32:48 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-04-16 15:32:48 +0000 |
| commit | 7a8e75266ff2c138f212a301de9774eafb2b3143 (patch) | |
| tree | 2d883a93dc1d62b835d20448b399b4b53d6556d4 /components/compositing/webview_manager.rs | |
| parent | af000d6c91f0958d6252b8e474cf596799001ae9 (diff) | |
| download | servo-7a8e75266ff2c138f212a301de9774eafb2b3143.tar.gz servo-7a8e75266ff2c138f212a301de9774eafb2b3143.zip | |
layout: Throw away nested marker elements instead of storing them in a `BoxSlot` (#36568)
`::before` and `::after` pseudo-elements can have their own `::marker`
pseudo-element. Since this case wasn't taken into account, they were
being stored in main element's `::marker` `BoxSlot`. This could cause
problems where two layout boxes would try to use the same `BoxSlot`. For
now, just don't store the nested version of the marker. Later, we'll
need to figure out how to store these layout objects without causing too
much memory usage.
Testing: This is covered by `/css/css-lists/nested-marker-styling.html`.
In
addition, we also made a test case that always causes this crash, but
since it
had to create 100000 `<div>`s it's probably not appropriate for a test
suite.
Fixes: #36551
Signed-off-by: Martin Robinson <mrobinson@igalia.com>
Co-authored-by: Oriol Brufau <obrufau@igalia.com>
Diffstat (limited to 'components/compositing/webview_manager.rs')
0 files changed, 0 insertions, 0 deletions