(also, if you're referring to how I stupidly had declared doctype in both my pages and my header.js, I fixed it)
Alright, I just read your source over - yeah, I see that Internet Explorer doesn't support (`content`), didn't realize. Although, to be fair, that 2.56% of the browser marketshare (and declining) aren't necessarily my target audience. I'll be sure to update my site though on the weekend to work with all browsers either way - but if you're using Internet Explorer, move on, pick up Vivaldi or Firefox or even just Edge
Oh, weird, maybe it's a version thing? (I'm on 66.0.3) ...actually, I just noticed, header.js is being served as absolute link to your NC... i think that's the problem, actually? (some sort of CORS issue) [here i come acting like a know-it-all and i didn't even check the line numbers on the console messages -- SMH]
Console Errors: Loading failed for the < script > with source “https://comfydev.neocities.org/header.js”. comfydev.com:14:1 An unbalanced tree was written using document.write() causing data from the network to be reparsed. For more information https://developer.mozilla.org/en/Optimizing_Your_Pages_for_Speculative_Parsing comfydev.com:59
I still stand by my assertion that manipulation of the DOM (rather than document.write) is the way to go being less error-prone. Vivaldi/chromium doesn't seem happy with document.write inserting < script > tags -- warnings in the console link to: https://www.chromestatus.com/feature/5718547946799104 and also: https://developers.google.com/web/updates/2016/08/removing-document-write
update: ok this is weird, my computer blue-screened, i opened firefox again, **saw your site load as intended**, then had to restart again due to my pc freezing, and now your site is not loading right *again*
Woah, weird. If that's happening where it's working occasionally but only when you get a BSOD, then it might be an issue on your end? It would make no sense for the site to work, and then not work, and then work again, seemingly related to computer crashes? Also yeah, I *did* notice that Google recommends against this, but the speed difference is marginal enough on even a slow connection not to make it my #1 priority
(...continued, stupid character limit grr) and even with a connection as slow as mine, a hard refresh with no cache is still pretty speedy. I'll be updating the templating system regardless but I can't tell if the issue you're having is related to my code because I've tested my site on both 65.0.2 and 66.0.3 with no issues and it only seems to happen on your end, and fixed itself after a crash.
I know the header fails to load properly if you're using PrivacyBadger on Firefox.
thank you invisibleup! it was privacy badger... i really got to learn to try disabling addons *before* assuming it's a website's fault. SMH at myself
Ohh yeah, privacy badger, i remember that causing issues with a friend of mine, it seems to like blocking the neocities site itself. I'll probably go through and change everything to relative references and see if that fixes things
A tag can only be a single word, and can only contain letters and numbers.
Select the tags you would like to remove:
You are going to block this site. This will do the following:
Are you sure you want to do this?