GitLab

This is done so that we don't need to switch the layout tree over to
legacy when entering printing, since that would cause some sort of state
loss, leaving the frames blank. The exact root cause is unknown. I spent
some time investigating it, but couldn't see what was wrong.

It really doesn't matter that much, though, since the only element in
the frameset document that would be an NG object would be the HTML root
element. We don't have NG-specific frame or frameset layout objects.
The frames themselves will still use LayoutNG (unless prevented by
something else), of course.

Bug: 1003815
Change-Id: Ic4dc470f5536ea8357ebccb624d43e9f30155728
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1875747Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708919}