commodorejohn
Veteran Member
Any chance of nuking this banner that's suddenly appeared? I know JS is disabled, thankyouverymuch; that's what I have a JS whitelist plugin installed for!
VCF Southwest | Jun 20 - 22 2025, | University of Texas at Dallas |
VCF Southeast | Jun 20 - 22 2025, | Atlanta, GA |
VCF West | Aug 01 - 02 2025, | CHM, Mountain View, CA |
VCF Midwest | Sep 13 - 14 2025, | Schaumburg, IL |
VCF SoCal | Feb 14 - 15, 2026, | Hotel Fera, Orange CA |
So why don't you want to enable JS for this site? Or is the issue that you do have JS enabled for this site (because it's in your allow list), but the site still thinks its disabled?Any chance of nuking this banner that's suddenly appeared? I know JS is disabled, thankyouverymuch; that's what I have a JS whitelist plugin installed for!
<noscript class="js-jsWarning">
<div class="blockMessage blockMessage--important blockMessage--iconic u-noJsOnly">
JavaScript is disabled. For a better experience, please enable JavaScript in
your browser before proceeding.
</div>
</noscript>
Well, some functionality can be done only with JS, and some of us find that functionality useful. So I do hope you're saying that there are things you want that can be done just as well without JS that you wish they had done without JS, rather than features that other people use should be removed because you personally don't feel the need for them and are annoyed that they exist.95% of the forum functionality works fine without it (oh, for the days when forum software was 100% functional without scripts!)
I just checked this out, and in my humble opinion it's not. It's at the head of threads, but not part of the fixed header so its scrolls off the top as you scroll down. For typical usage, where you're jumping directly to new messages in a thread, you won't even see it.Is the message terribly large and annoying, or something?
Humble or otherwise, that's your opinion and not mine. It's not a huge usability impediment, but it's irksome on principle.I just checked this out, and in my humble opinion it's not.
Also seeing this. I was assuming it was due to having JS disabled, but evidently it's just a failure of whatever dynamic-layout functionality the update might've added; the image is being loaded at full resolution, but getting scaled down to 100x10 for some reason.I don't get a javascript error (because I haven't disabled it), but the VCFED logo is teeny now, barely visible. You can see what it looks like on the screenshot in the above post.
I don't think it's a usability impediment at all, though I understand how you find it irksome. (Perhaps even irksome enough to suppress it in the way I suggested above, perhaps not.)It's not a huge usability impediment, but it's irksome on principle.
Yes, fixed now. Thank you and Happy Christmas.I figured that out, at least. For some reason, the upgrade caused the logo to resize to 100 pixels wide, and with the size of the logo file (572x58px) that translates to the tiny logo that we got.
Should be fixed, now, I believe.
- Alex
That's lovely; I disagree entirely. I do not need web designers presuming to tell me how I should have my browser configured. I have JS whitelisted because I mean to have JS whitelisted. (And frankly, the suggestion that this might ever be an "oops, didn't mean to do that...!" scenario when no mainstream browser comes configured by default to disable scripting is absurd.)I can only applaud developers who take the time and effort to explain why things are not working rather than just assuming end users have a particular common configuration of their browser.
They are not suggesting that you have misconfigured your browser. They are simply informing you that they have features that depend on JavaScript to which you're won't have access. This is quite the opposite of, "we'll just let the site quietly break if you don't turn on what we want you to turn on."That's lovely; I disagree entirely. I do not need web designers presuming to tell me how I should have my browser configured. I have JS whitelisted because I mean to have JS whitelisted. (And frankly, the suggestion that this might ever be an "oops, didn't mean to do that...!" scenario when no mainstream browser comes configured by default to disable scripting is absurd.)
You and I are both free to speculate about the developers' attitudes, and we may disagree - but kindly do not presume to tell me what my motivation is here.The absurd thing is that you know how to turn off that message, but you can't be bothered to put in a tiny bit of effort to do so, instead complaining that someone else won't hid this in order to make you feel better
Ok, let's just say it comes across that way, then, even if by "I do not need web designers presuming to tell me..." you really meant, "I'm sure the web developers are doing there best to make things work as well as possible for everyone, overall, and I understand and accept that perhaps what I want is not what most of the world wants."...but kindly do not presume to tell me what my motivation is here.