RESOLVED FIXED Bug 209695
[RenderTreeBuilder] Destroy the child first in RenderTreeBuilder::destroyAndCleanUpAnonymousWrappers
https://bugs.webkit.org/show_bug.cgi?id=209695
Summary [RenderTreeBuilder] Destroy the child first in RenderTreeBuilder::destroyAndC...
zalan
Reported 2020-03-27 20:49:27 PDT
Before destroying a renderer we check if this renderer is inside an anonymous wrapper (including ancestors) and if so, we get rid of these wrappers too the same time. However because of the 'leaf -> container' tear down direction, we need to destroy the child first.
Attachments
Patch (4.98 KB, patch)
2020-03-27 20:55 PDT, zalan
no flags
Patch (5.43 KB, patch)
2020-03-28 09:50 PDT, zalan
no flags
zalan
Comment 1 2020-03-27 20:55:07 PDT
Antti Koivisto
Comment 2 2020-03-28 00:14:57 PDT
If this is the order we want we should probably change RenderTreeBuilder::destroy instead.
zalan
Comment 3 2020-03-28 06:25:16 PDT
(In reply to Antti Koivisto from comment #2) > If this is the order we want we should probably change > RenderTreeBuilder::destroy instead. Yeah, that's a good point. I would guess the ::destroy() is only called with the bottom-most renderer from the updater, and only the builder calls it with depth (in case of anon wrappers).
zalan
Comment 4 2020-03-28 08:07:19 PDT
(In reply to zalan from comment #3) > (In reply to Antti Koivisto from comment #2) > > If this is the order we want we should probably change > > RenderTreeBuilder::destroy instead. > Yeah, that's a good point. I would guess the ::destroy() is only called with > the bottom-most renderer from the updater, and only the builder calls it > with depth (in case of anon wrappers). Actually we tried that here https://trac.webkit.org/changeset/228606/webkit and had to revert.
zalan
Comment 5 2020-03-28 09:50:40 PDT
EWS
Comment 6 2020-03-28 10:21:48 PDT
Committed r259160: <https://trac.webkit.org/changeset/259160> All reviewed patches have been landed. Closing bug and clearing flags on attachment 394825 [details].
Radar WebKit Bug Importer
Comment 7 2020-03-28 10:22:13 PDT
Note You need to log in before you can comment on or make changes to this bug.