Avoid fragment activation while rendering blocked
This bug was introduced by: https://crrev.com/dbd4eed1920a2aafbc87236db7efb98f108ba063 The previous behavior was to only ProcessUrlFragment if rendering was ready. If it wasn't, we would mark it as needing processing and try again when it becomes ready. My patch above separated ProcessUrlFragment from ScrollAndFocusFragmentAnchor but omitted the deferral of the latter in cases where rendering wasn't yet ready. This patch simply early-outs in ScrollAndFocusFragmentAnchor when rendering isn't yet ready to match the old behavior. It also adds back a hook in ImplicitClose since a layout may not be needed at the time the document was closed because it was done at a time when rendering was still blocked. Bug: 851338 Change-Id: I70d4ab233580f7c005fd56e805d5acd79cd4eee6 Reviewed-on: https://chromium-review.googlesource.com/1130958Reviewed-by:Kent Tamura <tkent@chromium.org> Commit-Queue: David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#583146}
Showing
Please register or sign in to comment