3 ms·
I've tracked down the root cause: I needed to disable two uBlock Filters in order to successfully load the page: Fanboy's Annoyance and Fanboy's Social. It seem
by yakubin 4y ago
I've tracked down the root cause: I needed to disable two uBlock Filters in order to successfully load the page: Fanboy's Annoyance and Fanboy's Social. It seems that they block some JS related to social buttons (https://japan-dev.com/assets/socialButton.9ddbb1cc.js https://japan-dev.com/assets/socialButton.9ddbb1cc.js) and that makes the rest of JS responsible for the rest of the page to not execute (due to a failed request).
Sorry for the false flag.
- emptyparadise 4y agoDoesn't load in Safari for me with ad blockers.
- etdev 4y agoInteresting, can you let me know which ad blocker so I can try to reproduce?
- emptyparadise 4y agoI think it's the same social media filters that did it. For reference, I'm using AdGuard on iOS and have the social media button filters on.
- etdev 4y agoOh wow thanks for checking, that's helpful to know. I should probably restructure things so that one component failing doesn't bring down the whole site if I can...
- jmnicolas 4y agoI'm on Windows, blank page with Firefox and uBlock origin. Works fine on Ms Edge (no ad blocker).
- webmobdev 4y agoYeah, I still get a blank page. (I hope you don't expect us to disable uBlock Origin to see some social media buttons because that's never happening!).
- 3np 4y agoYes, you definitely should. Adblockers is just one reason why networks requests don't always go through successfully expected. I also get a sha512 mismatch on the CF script. (Degrading gracefully so content is readable even without client-side JS is an even better idea but that obv takes more effort to sort out on an existing SPA) Looking forward to reading your article but my reverse-engineering stops here for now (:
- deleted 4y ago[deleted]