зеркало из https://github.com/mozilla/gecko-dev.git
de3979ca1f
BrowsingContext::ShouldAddEntryForRefresh expects to be passed the current URI, to determine if it's the same as the URI for the new load (we shouldn't add a new entry if they are the same). Before this patch, in the child process we call BrowsingContext::ShouldAddEntryForRefresh from nsDocShell::MoveLoadingToActiveEntry (nsDocShell::CreateContentViewer -> Embed -> MoveLoadingToActiveEntry), passing nsDocShell's mCurrentURI. However, by that point nsDocShell::CreateContentViewer has already set the mCurrentURI to the newly loading URI (through nsDocShell::OnNewURI). In the parent process we do pass the correct URI to BrowsingContext::ShouldAddEntryForRefresh, so the session history ends up being correct, but depending on timing of the IPC messages there's a brief moment where index and length are incorrect in the child process (child process and parent process get a different answer from BrowsingContext::ShouldAddEntryForRefresh). This causes intermittent failures in the test at docshell/test/mochitest/test_bug1742865.html. Differential Revision: https://phabricator.services.mozilla.com/D169544 |
||
|---|---|---|
| .. | ||
| base | ||
| build | ||
| shistory | ||
| test | ||
| moz.build | ||