airforcetimes renders incorrectly |
|||||||
Issue descriptionChrome Version : 54.0.2840.24 / 55.0.2862.3 OS Version: 8743.25.0 & 8816.0 URLs (if applicable) : https://www.airforcetimes.com/articles/u-2s-flight-routine-before-fatal-crash-air-force-says Repro on veyron_minnie: 55.0.2842.0 / 8753.0.0 Repro on peach_pi: 54.0.2822.0 / 8687.0.0 No repro on: samus 52.0.2743.116 / 8350.68.0 What steps will reproduce the problem? 1. https://www.airforcetimes.com/articles/u-2s-flight-routine-before-fatal-crash-air-force-says 2. 3. What is the expected result? No funny "{{#if sponsored..." characters over-laid on web content. What happens instead of that? Funny "{{#if sponsored..." characters over-laid on web content. Please provide any additional information below. Attach a screenshot if possible. UserAgentString: Mozilla/5.0 (X11; CrOS aarch64 8743.25.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.24 Safari/537.36 From Feedback report: https://feedback.corp.google.com/#/Report/13691836469
,
Sep 22 2016
Chrome Developer tools "Console" log (on elm, 54.0.2840.24): Mixed Content: The page at 'https://www.airforcetimes.com/articles/u-2s-flight-routine-before-fatal-crash-air-force-says' was loaded over HTTPS, but requested an insecure image 'http://snagfilms.s3.amazonaws.com/f7/51/536221ee4a0780ee81f533a32cb8/u-2-crash-wreckage.jpg'. This content should also be served over HTTPS. u-2s-flight-routine-before-fatal-crash-air-force-says:1586 Mixed Content: The page at 'https://www.airforcetimes.com/articles/u-2s-flight-routine-before-fatal-crash-air-force-says' was loaded over HTTPS, but requested an insecure image 'http://snagfilms.s3.amazonaws.com/12/f3/667356d54ae9bf0c1934568deced/air-force-col-larry-broadwell.jpg'. This content should also be served over HTTPS. initialize.js?build=20160915-0159:314 sightline/masthead Object initialize.js?build=20160915-0159:314 sightline/article/article-page Object initialize.js?build=20160915-0159:371 [INIT] module without data, leave as is Object initialize.js?build=20160915-0159:371 [INIT] module without data, leave as is Object initialize.js?build=20160915-0159:371 [INIT] module without data, leave as is Object initialize.js?build=20160915-0159:371 [INIT] module without data, leave as is Object initialize.js?build=20160915-0159:371 [INIT] module without data, leave as is Object initialize.js?build=20160915-0159:314 global/comments Object initialize.js?build=20160915-0159:371 [INIT] module without data, leave as is Object initialize.js?build=20160915-0159:314 noop Object initialize.js?build=20160915-0159:371 [INIT] module without data, leave as is Object initialize.js?build=20160915-0159:371 [INIT] module without data, leave as is Object initialize.js?build=20160915-0159:371 [INIT] module without data, leave as is Object initialize.js?build=20160915-0159:314 sightline/footer Object initialize.js?build=20160915-0159:371 [INIT] module without data, leave as is Object initialize.js?build=20160915-0159:444 Trying to instantiate typeahead search initialize.js?build=20160915-0159:1250 Calling FB.init() initialize.js?build=20160915-0159:213 [GLOBAL/COMMENTS] No Div for id: 00000155-3b01-dd0e-adf5-ff5152b30000 u-2s-flight-routine-before-fatal-crash-air-force-says:3294 [NOOP] Post Process tmpModule u-2s-flight-routine-before-fatal-crash-air-force-says:2439 [SIGHTLINE/FOOTER] Post Process u-2s-flight-routine-before-fatal-crash-air-force-says:2887 [SIGHTLINE/MASTHEAD] Post Process initialize.js?build=20160915-0159:401 status: Object initialize.js?build=20160915-0159:1259 FB LOGIN STATUS Object u-2s-flight-routine-before-fatal-crash-air-force-says:3324 [SIGHTLINE/ARTICLE/ARTICLE-PAGE] Post Process initialize.js?build=20160915-0159:383 [INIT] 5 modules resolved www.facebook.com/sw?s=push:1 Service Worker termination by a timeout timer was canceled because DevTools is attached.
,
Sep 22 2016
,
Sep 22 2016
Looks like it's Handlebars to me (http://handlebarsjs.com/). There's some script presumably that is failing to load or execute on some new version of Chrome, which means that the handlebars directives are never replaced.
,
Sep 22 2016
Ah, actually, given that log, looks like perhaps a change in HTTPS policy causing some required resource to not load. +emilyschecter
,
Sep 22 2016
+mkwst, any ideas what this is from?
,
Sep 25 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 28 2017
,
Oct 2 2017
Closing. This is a year old, and the link no longer works. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by abodenha@chromium.org
, Sep 22 2016The {{#if published stuff is some sort of script language in the page source which doesn't look to be getting properly processed so it renders as text. If you pop up the dev console is there any sort of JS error when this happens? I don't think this is a layout issue. More likely something about the affected devices exposing a bug in the page.