Issue metadata
Sign in to add a comment
|
NavigationTestCase/testRestoreHistoryToNTPAndNavigateForward fails with new NTP and WKBasedNavigationManager |
||||||||||||||||||||||
Issue descriptionNavigationTestCase/testRestoreHistoryToNTPAndNavigationForward is failing on ToTT (0e55d4452afdab2949faf5141aac8224626bcefc) when --enable-features=SlimNavigationManager is used. Failure message: ../../ios/chrome/test/earl_grey/chrome_earl_grey.mm:215: error: -[NavigationTestCase testRestoreHistoryToNTPAndNavigateForward] : Exception: AssertionFailedException Exception Name: AssertionFailedException Exception Reason: (([condition waitWithTimeout:base::test::ios::kWaitForUIElementTimeout]) is true) failed Exception Details: Failed waiting for web view containing pony The problem seems to be that the go forward after a session restore doesn't dismiss the NTP. I can reproduce this by going through the same steps in the test manually: 1. Load NTP 2. Navigate to any page (e.g. wikipedia.org) 3. Tap Back button 4. Force app crash (in simulator, just relaunch the simulation) 5. Wait for NTP is restored 6. Tap Forward button Expected: wikipedia.org should load Actual: NTP is still visible, but omnibox is show at the normal location of a web view. Video is attached.
,
Nov 15
,
Nov 15
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/4ca449e4c3aaeb36393c855ef259c5ee9d028e84 commit 4ca449e4c3aaeb36393c855ef259c5ee9d028e84 Author: Danyao Wang <danyao@chromium.org> Date: Thu Nov 15 21:47:02 2018 [Nav Experiment] Temporarily disable broken NavigationTestCase test. Bug: 905688 Change-Id: I11f0b6320ba8221139323a285199a5570afab429 Reviewed-on: https://chromium-review.googlesource.com/c/1338308 Reviewed-by: Eugene But <eugenebut@chromium.org> Commit-Queue: Danyao Wang <danyao@chromium.org> Cr-Commit-Position: refs/heads/master@{#608526} [modify] https://crrev.com/4ca449e4c3aaeb36393c855ef259c5ee9d028e84/ios/chrome/browser/web/navigation_egtest.mm
,
Nov 16
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/6bd66a17cc064a97ccda63b35921c3fa55731ab4 commit 6bd66a17cc064a97ccda63b35921c3fa55731ab4 Author: Danyao Wang <danyao@chromium.org> Date: Fri Nov 16 22:18:32 2018 [Nav Experiment] Handle about:newtab when traversing restored history. Navigating away from an app-specific URL in restored session history is a special case that requires a reload to trigger theclient-side redirect in restore_session.html. about:newtab, which is used by the BrowserContainerContainsNTP feature, should be treated as an app-specific URL for this case. This fixes the regression in NavigationTestCase/testRestoreHistoryToNTPAndNavigateForward after enabling BrowserContainerContainsNTP. Bug: 905688 Change-Id: I96d4612152a003f3c7275720a01eb6376c3ff806 Reviewed-on: https://chromium-review.googlesource.com/c/1340761 Commit-Queue: Danyao Wang <danyao@chromium.org> Reviewed-by: Justin Cohen <justincohen@chromium.org> Reviewed-by: Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#608982} [modify] https://crrev.com/6bd66a17cc064a97ccda63b35921c3fa55731ab4/ios/chrome/browser/web/navigation_egtest.mm [modify] https://crrev.com/6bd66a17cc064a97ccda63b35921c3fa55731ab4/ios/web/web_state/ui/crw_web_controller.mm
,
Nov 16
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by danyao@chromium.org
, Nov 15