Site lies about 3rd-party javascript
See original GitHub issueVisiting filterlists.com with js disabled says:
We do not use any third-party JavaScript, and your privacy is very important to us.
Yet there’s a script from cdn.polyfill.io
.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
How do developers trust that 3rd party js isn't copying & ...
How do developers trust that 3rd party js isn't copying & sending data to another source ; u/samjmckenzie avatar. samjmckenzie · 16 ;...
Read more >Third-Party Scripts on Websites Present a 'Broad & Open' ...
Typically, when a webpage calls a third-party script, it is loaded directly into a browser from an external server belonging to the third...
Read more >Third Party JavaScript Management Cheat Sheet
Website with the collection of all the cheat sheets of the project.
Read more >How to prevent third-party scripts to take over? - JavaScript
Is there a way to make a part of the page more isolated against third party scripts? One way I see is the...
Read more >Why SREs Should Worry More About Third-Party JavaScript
Third-party JavaScript attacks on websites are on the rise. According to prominent security researcher Graham Cluley, tens of thousands of ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It was added in an (ultimately failed) attempt to get the site to load in Internet Explorer 11, as a quick Google search told me that such a polyfill script was by far the easiest solution to get around the “Promise is undefined” error.
However, after the script was added, it turned out that IE11 was still throwing a fit about a dozen different JS elements, so I guess that the polyfill script can be removed for now if needed (presuming it wouldn’t be worth it for now to convert it to a 1st-party script).
closed by #753