2 ms·
This page does not contain an article for me. Simply a header, an ad, and some blocked content. I am not blocking scripts, and there are no errors in the cons
by reificator 7y ago
This page does not contain an article for me. Simply a header, an ad, and some blocked content.
I am not blocking scripts, and there are no errors in the console. The only network requests that are failing are analytics requests that are being blocked. The HTML source does not appear to contain an article that has failed to load. None of the requests appear to be for article content, just a lot of libraries, stylesheets, and images.
Interesting snippets I found while reading the source:
<!-- real people should not fill this in and expect good things - do not remove this or risk form bot signups-->
I'm guessing they have a fake form honeypot to prevent bots from spamming their real signup form?
/* <![CDATA[ */
var newsletter = {"messages":{"email_error":"Email address is not correct","name_error":"Name is required","surname_error":"Last name is required","privacy_error":"You must accept the privacy policy"},"profile_max":"20"};
/* ]]> */
I can tell from this snippet I really don't want to see their build pipeline if they have to escape such a simple statement such that it won't break XML or JS.
- autoexec 7y agoIf we can't read the article we can at least judge their code, like the 18 lines of JavaScript and CSS to display an emoji, or the fact that the entire text of the article is missing.
- benologist 7y agoStuff like /* <![CDATA[ */ was common some years ago because of JS and XHTML parsers colliding - https://magento.stackexchange.com/questions/164569/put-cdata-it-is-a-good-practice-or-not-necessarily-magento-1-9 https://magento.stackexchange.com/questions/164569/put-cdata...
- reificator 7y agoYou know what, my bad. I don't think I ever tried to use inline JS in that era. Thanks for that tidbit of info. I was picturing some horrific build script with the canonical JS stored in XML.