Regression: Unable to see output in JSbin files on chrome builds |
|||
Issue descriptionChrome Version: 66.0.3343.0 OS: Mac 10.13.3, Ubuntu 14.04 and Windows 10 What steps will reproduce the problem? (1) Open any of JSBin files and observe for output EX:1. http://jsbin.com/girazef/edit?js,output 2. http://jsbin.com/verubipejo/ Expected: Should be able to see output Actual: Unable to see output results in JSbin files. This issue is working fine in M64 stable 64.0.3282.140 Will update bisect results in a while
,
Feb 10 2018
Last good build: 66.0.3334.0 First bad build: 66.0.3335.0 Changelog: =========== https://chromium.googlesource.com/chromium/src/+log/e93a97278842441acc34611ec2ccc0b50c13fb6b..c646e48f1ff851d8eb8e2ae713a031684b46db27 rsleevi@: Could you please take a look at this. Thank you!
,
Feb 11 2018
If you look in the Chrome 64 DevTools, you'll see the warning that this site will be distrusted in Chrome 66. This is part of the phasing-out of trust in Symantec's legacy PKI at https://security.googleblog.com/2017/09/chromes-plan-to-distrust-symantec.html |
|||
►
Sign in to add a comment |
|||
Comment 1 by ajha@chromium.org
, Feb 9 2018