Issue metadata
Sign in to add a comment
|
Using History API pushState and navigating back or forwards results in browser displaying HTTPS connected site as HTTP UI-wise
Reported by
andresan...@gmail.com,
Sep 23 2016
|
||||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. Visit a site that uses history.pushState() and HTTPS such as 'https://css-tricks.com/examples/State/' 2. Select an option that would result in execution of the pushState function 3. Press the back button/key (or/and forwards) ... or ... 1. Visit any site that uses HTTPS 2. Run something along the lines of "javascript:history.pushState('data', null, '/foobar')" in the URI bar 3. Press the back button/key (or/and forwards) What is the expected behavior? The browser should be reporting the HTTPS site with the appropriate security status, padlock and if available, EV. Just like the desktop Chrom(e/ium) browsers. What went wrong? - URL is being treated as HTTP (padlock icon disappears as well as the green HTTPS [changes to colour used for HTTP]) - Site information button (circled 'i' icon in the menu) also treats site as HTTP (states that connection is not private). Did this work before? N/A Chrome version: 53.0.2785.116 Channel: dev OS Version: 6.0.1 Flash Version: Shockwave Flash 23.0 r0
,
Sep 24 2016
,
Sep 26 2016
,
Sep 28 2016
Can reproduce for dev channel, not for beta or stable. I believe this is a duplicate of 647683.
,
Sep 28 2016
P.S. Thank you for the bug report! |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by andresan...@gmail.com
, Sep 23 2016