Source code is blank when DevTools is opened - page has to be refreshed
Reported by
brand.pe...@gmail.com,
Dec 14 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36 Steps to reproduce the problem: 1. Open https://law74.co.za/login.php?co=la 2. Press F12 3. Observe that code for login.php page is blank in DevTools source list. What is the expected behavior? One should be able to see the source of the page to be able to insert javascript breakpoints etc. What went wrong? The page source was blank so I was unable to insert javascript breakpoints. Reloading the page while DevTools window is open does then show the source of the page, but that loses all the interaction that I had with the page and costs me time and effort to repeat. Did this work before? N/A Chrome version: 63.0.3239.84 Channel: stable OS Version: 10.0 Flash Version: none In order to find the cause, I wrote another page which delivers the same HTML and javascript code, but does less php coding in the background. Repeat the above for https://law74.co.za/login2.php?co=la, and for some reason the source IS visible. Is this a timing issue or something in the HTTP headers?
,
Dec 14 2017
Bisect info: 343550 (good) - 343564 (bad) https://chromium.googlesource.com/chromium/src/+log/ffab7376..07d8ae55?pretty=fuller If I have to guess it would be r343563 "Roll WebKit" and a43613d84570d06cbd3cd9c46b77d6d54486b028 inside: "[DevTools] Do not report edited resources via Page.getResourceContent." Instead of requesting scripts through Page.getResourceContent, we should use Debugger.getScriptSource or CSS.getStylesheetTest. Landed in 46.0.2484.0
,
Dec 14 2017
@dgozman - not sure if this is related to your change, might be related to a very old change that woxxom bisected to.
,
Dec 14 2017
Thank you for filing an issue! This is a known problem: we do not retain main resource and can only show the content if it was cached on disk. Unfortunately, there is no feasible way to fix this.
,
Dec 15 2017
On further investigation, the critical change between login.php and login1.php is a call to php function session_start(); adding and removing that call causes the symptoms as reported. Does this php function cause chrome to loose the cache to the main resource? Try the attached file, then comment out line 4 "session_start".
,
Nov 29
Issue 909766 has been merged into this issue. |
|||
►
Sign in to add a comment |
|||
Comment 1 by gov...@chromium.org
, Dec 14 2017Labels: Needs-Triage-M63