Chrome shows previously loaded page (AFTER hiding it) during http auth
Reported by
teo8...@gmail.com,
Jun 22 2018
|
|||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36 Steps to reproduce the problem: 1. go to http://google.com (or any other website for that matter) 2. go to a website that requires http authentication 3. when prompted, enter the http auth credentials and submit them What is the expected behavior? At step 2, when the prompt popup form for http auth credentials is shown, the contents of the website previously loaded is not shown anymore. And when you do enter and submit the username and password, nothing should show up in the tab until the contents of the new page are loaded What went wrong? At step two, while the prompt for http auth credentials is shown, the contents of the website previously loaded are hidden, as expected. However, when you do submit the credentials, the previous website suddenly shows up, until the new one is loaded and replaces the previous one. This gives the false impression that the previous webpage is reloaded again (if that is actually the case, then it's even more wrong). Did this work before? N/A Chrome version: 67.0.3396.87 Channel: stable OS Version: Flash Version: This is so fucking stupid.
,
Jun 25 2018
teo8976@ Thanks for the issue. Tested this issue on Ubuntu 17.10 and tried searching for a site which requires http authentication, but unable to find one. Request you to provide a sample site with credentials which will help in further triaging of the issue. Thanks..
,
Jun 25 2018
Sorry I don't have one that I can share. You mean you don't have a server where you can create one?
,
Jun 25 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 25 2018
BTW it seems you didn't try very hard. Here's one I found googling for "test http auth": https://jigsaw.w3.org/HTTP/Basic/ user "guest" password "guest"
,
Jun 25 2018
However, I think the above loads too fast to be able to observe the issue.
,
Jul 17
Unable to reproduce the issue on reported chrome version 67.0.3396.87 and latest chrome stable 67.0.3396.99 using Ubuntu 17.10. Attaching screen-cast for reference. Steps: --------- 1. Launched reported chrome 2. Navigated to given URL in comment # 5 >> " https://jigsaw.w3.org/HTTP/Basic/ " 3. Opened multiple tabs on browser window and navigated to URL "https://www.youtube.com/" 4. Entered Credentials As we have not seen previous page after login. @Reporter: Could you please review the attached screen-cast and confirm if anything being missed here. Could you please upgrade to latest chrome stable 67.0.3396.99, you can download latest chrome builds here:" https://www.chromium.org/getting-involved/dev-channel " and let us know if issue still persists. Thanks.!
,
Jul 17
> @Reporter: Could you please review the attached screen-cast and confirm if anything being missed here. I can't, because (1) I'm not going to watch TWENTY-FOUR MINUTES of screencast and (2) having watched what seems likely to be the relevant part (i.e. until it becomes still) I don't see you entering the credentials at all. Anyway, assuming you are reproducing the steps in the original report (BTW you mention opening multiple tabs, you shouldn't do that: this issue is observed by doing all in ONE TAB), you need the url with http authentication to take some time to load. Unfortunately the one I provided loads too fast, so you won't have time to observe the issue anyway.
,
Jul 17
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 25
As per comment #8 tested this issue and as we are Unable to reproduce the issue on reported chrome version 67.0.3396.87 and latest chrome stable 68.0.3440.75 using Ubuntu 17.10. Note: As per comment #8 if possible provide new URL for better triaging it >>"Unfortunately the one I provided loads too fast, so you won't have time to observe the issue anyway". @Reporter: Could you please upgrade to latest chrome stable 68.0.3440.75, you can download latest chrome builds here:" https://www.chromium.org/getting-involved/dev-channel " and let us know if issue still persists. Thanks..!
,
Jul 25
> Note: As per comment #8 if possible provide new URL for better triaging it So what exactly have you tested? If you tested with the url in comment 7, of course you don't observe the issue, it loads too fast. Is it so difficult for you to create a page on a server that requires http authentication and takes a few seconds to load (e.g. with a sleep command on the server side)? I can do that myself in 15 minutes, only I don't like wasting my time doing someone else's job.
,
Jul 25
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 25
> only I don't like wasting my time doing someone else's job Ok, so I did, and I have been able to recreate a reproducible example. Admittedly, there was more to it than just the http-authenticated page taking long to load (my suggestion in comment 11 would not reproduce the issue). However, I would have expected you to at least try that before saying you couldn't reproduce and putting the bug into Needs-Feedback status. It took me the same trial-and-error investigative effort that it could have taken you to recreate the reproducing test case. Here's how to reliably reproduce the issue (exactly as described in the original report except now I have a test URL that reproduces the issue and that I can share): ------------ 1. go to http://php.net (or any other website for that matter) 2. go to http://matteosistisette.com/test/stupidchrome/httpauth/ 3. when prompted, enter the http auth credentials: user: test passwd: test77 What went wrong? At step two, while the prompt for http auth credentials is shown, the contents of the website previously loaded are hidden, as expected. However, when you do submit the credentials, the previous website suddenly shows up, until the new one is loaded and replaces the previous one. ----------- Apparently what triggers the issue is the presence of <script> tags with a 'src' attribute in the page (I haven't tried without src). NOTE: the fact that in these case none of the urls in the scripts' src attribute exists in not relevant. In my original reproducing scenarios, all files exist. The more <script> tags I add to the page, the longer you can see the previously loaded page. The less there are, the shorter, and with less than 3 I don't observe the issue at all. (P.S. note that almost any real-life page requiring http authentication would have reproduced the issue, since the majority of real-life web pages have three javascript scripts or more.)
,
Jul 26
Able to reproduce the issue on reported chrome version 67.0.3396.87 using Ubuntu 17.10. As the issue is not seen in earlier versions(60.0.3112.0) hence considering it as Regression and marking it as Untriaged. Adding Needs-Bisect label, will update the bisect info soon. Thanks..!
,
Jul 27
Able to reproduce the issue on reported chrome version 67.0.3396.87 also on latest chrome 70.0.3503.0 using Mac 10.13.5, Ubuntu 17.10 and Windows 10.
NOTE: 1. Inconsistent behavior seen on Mac from M-60 to M-70
2. On Windows and Ubuntu observed Blank screen before loading the page on M-60
Same behavior is seen on M60(60.0.3112.113) hence considering it as non-regression and marking it as Untriaged. And removing Needs-Bisect label.
Thanks!
,
Jul 27
,
Nov 22
***Mass UI Triage*** Hi, Just to update: We were unable to reproduce this bug on Mac(10.13.1, 10.13.4,10.14.2), Windows(7,8,8.1,10) and Linux(14.04) OS using Latest canary #72.0.3617.0 Hence, marking it as WontFix. If this bug still reproduces for you, please reopen or file a new issue. Thank you.
,
Dec 19
> We were unable to reproduce this bug (...) using Latest canary #72.0.3617.0 > > **Hence**, marking it as WontFix. If that is the case, the correct status would be FIXED. |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by krajshree@chromium.org
, Jun 24 2018