New issue
Advanced search Search tips

Issue 847423 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jun 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 1
Type: Bug



Sign in to add a comment

Blank page is displayed on navigating forward and backward

Project Member Reported by pmadalla@chromium.org, May 29 2018

Issue description

App Version: 68.0.3440.6 Beta
iOS Version: 11.3.1,10.3.3
Device: iPhone,iPad

Precondition:
1.Enable “web-error-pages” from chrome://flags

Steps to reproduce:
  1. Launch chrome.
  2. Goto ndtv1234.com
  3. Now go to facebook.com in the same page.
  4. Disable the wifi and Mobile data
  5. Goto whatever.com in the same webpage.
  6. Tap on back arrow and navigate back to facebook.com
  7. Enable Wifi
  8. Tap on back arrow.
  9. Tap on back arrow and go to ntp
 10. Tap on Forward arrow in NTP

Observed results: 
Blank page is displayed on tapping on Forward arrow in NTP

Note :
Works fine on disabling "web-error-pages" the flag

Expected results: 
Blank page should not be displayed

Number of times you were able to reproduce: 3/5
Bug reproducible after clean install: Yes
Bug reproducible after clearing cache and cookies: Yes
Bug reproducible on Chrome Mobile on Android: NA
Bug reproducible on Safari/Firefox: Firefox: NA, Safari: NA
Bug reproducible on current stable build (App Version, iOS Version): NA on M66 and 67
Bug reproducible on the current beta channel build (App Version, iOS Version): Yes in M68

Link to video/image:  
https://drive.google.com/file/d/1j8-zEj6YhZ4hESeQV4NysTVfXI55uTGZ/view?usp=sharing


 
Labels: zine-triaged
Components: -UI>Browser>NewTabPage Mobile>WebView>Glue
Labels: ReleaseBlock-Stable M-69
Owner: eugene...@chromium.org
Status: Assigned (was: Untriaged)
Labels: -Pri-2 -zine-triaged Pri-1
Labels: Needs-Feedback
I can not reproduce the bug by following Steps to reproduce and the video does not match steps to reproduce. Could you please update the bug description with working steps.
Pramod, could you please test with and without "slim-navigation-manager" enabled. Maybe this bug is triggered by a different feature.
Labels: -Needs-Feedback
Issue is reproducible on disabling slim navigation manager feature.
Updating the steps and video.

Steps to repro :
1. Launch chrome.
2. Goto ndtv1234.com
3. Now go to facebook.com in the same page.
4. Disable the wifi and Mobile data
5. Goto whatever.com in the same webpage.
6. Tap on back arrow and navigate back to facebook.com
7. Enable Wifi
8. Tap on back arrow and navigate to ndtv.com
9. Tap on Forward arrow and navigate to facebook.com
10. Tap on back arrow and navigate back to NTP
11. Tap on Forward arrow in NTP

Video :
https://drive.google.com/file/d/1-HWmuJ0XB_bsQigSwb19mOrw69ii3pfp/view?usp=sharing
Labels: Needs-Feedback
I have a few questions:

1.) Could you please clarify step 10. Do I have to tap back twice (first to load ndtv1234.com and then again to load NTP)?
2.) Is this bug reproducible when slim navigation manager feature is enabled?
3.) After step 6 the navigation never finishes and I stuck with whatever.com (see screenshot). Do you see the same behavior?
IMG_5882.PNG
20.3 KB View Download
Labels: -Needs-Feedback
Hi Eugene

Below are the findings for above question

1. Could you please clarify step 10. Do I have to tap back twice (first to load ndtv1234.com and then again to load NTP)?
 
-- Yes we need to tap back arrow twice to navigate back to NTP i.e tap back arrow to ndtv1234 and then tap back arrow and navigate back to ntp.

2. Is this bug reproducible when slim navigation manager feature is enabled?

 -- Works fine when the Slim navigation manager is enabled

3. After step 6 the navigation never finishes and I stuck with whatever.com (see screenshot). Do you see the same behavior?

 -- I can navigate back from whatever.com

Cc: -eugene...@chromium.org
Status: WontFix (was: Assigned)
Thanks Pramod!

With 68.0.3440.9 after step 6 I can navigate back from whatever.com
With 69.0.3447.0 after step 6 navigation from whatever.com never finishes (crbug.com/848802)

I'm closing this bug, because we not going to ship “web-error-pages” in M68 and it's not possible to get past step 6 in M69. The bug which happens on step 6 is tracked separately (crbug.com/848802).


Sign in to add a comment