Spec-align resolving history handling during navigation #34747
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Makes use of the
is_initial_about_blank
property onDocument
in order to determine whether a navigation should create a history entry, or replace the current history entry.This unfortunately introduces a new intermittent failure (
/html/browsers/browsing-the-web/navigating-across-documents/initial-empty-document/iframe-nosrc.html
, example). Initially I thought I should not push the change and open this PR, but it appears to belong in the family of intermittents that Gregory was looking into in #31973 and a little more spec alignment might be useful - but happy to close this if it's an issue.Try
./mach build -d
does not report any errors./mach test-tidy
does not report any errors