Before the content even loaded there was a light box that blacked out the content behind it asking for my email.
Why on earth is anyone going to sign up for your mailing list when at this point, they haven't yet had a chance to read anything on your site?
If you must insist on a sign up box, put it at the end of the article (and preferably after the article, not hiding the text).
The more people we are, the greater the chances that the web remains usable without JavaScript.
Until now most content-heavy sites (like most university sites) are not problematic for the most part (1). Which I suppose is why there's no complaining till now. By having a healthy community of users with JS disabled, hopefully there will be enough complaints when it gets worse.
(1) the static parts, which is most URLs used during the day. If I encounter a site that requires JS to log in, I'll open a separate browser with JS. If I encounter a page that only shows the content with JS, I just close it unread, unless in the very rare case that it's important to me (most important content is still not relying on JS).
I think the idea that you need Javascript to drive a page designed to show an article consisting of text and images is probably worth questioning. Maybe you do, I don't know. But I think you should at least think about instead of falling back on the idea that the web is Javascript-driven.
You (probably) won't be benefiting the people without Javascript because hopefully your page works for them anyway. (Astoundingly, some simple article-type pages do not.) You will be benefiting yourself and almost all users because, without JS, your site will load faster and (often as not on really JS-heavy websites) scroll faster.
If you're creating a webapp, sure, you'd be crazy not to use Javascript.
But it's insane that Internet comment threads or text-based articles can drive yy i7 to 100% usage.
S = 'N';
s = s + 'o';
s = s + ',';
s = s + ' ';
s = s + 'n';
s = s + 'o';
s = s + ' ';
s = s + 'i';
s = s + 't';
s = s + ''';
s = s + 's';
s = s + ' ';
s = s + 'r';
s = s + 'e';
s = s + 'a';
s = s + 'l';
s = s + 'l';
s = s + 'y';
s = s + ' ';
s = s + 'n';
s = s + 'o';
s = s + 't';
s = s + '.';
$("comment_field").innerText = sIf you want static documents, I recommend pdfs?
Which of course aren't viewable in a terminal.
The Web is about the interchange of documents, and documents are text.
That's a silly criteria.
Books on art, magazines, maps, etc. are all definitely documents and aren't view-able in a terminal.
The web was never about interchange of documents, where'd you dream up that fantasy?
I'm kind of surprised how dense the ret-con fantasies here are about the web considering this is a pretty technical forum.
> The web was never about interchange of documents
See also http://www.anybrowser.org/campaign/, your perception of what is and isn't viewable in a terminal, and what should be, is strange for somebody who claims to know the web's history.
The Web has literally never been about VT100 text document displays. I'm not sure why this is hard to understand. That was gopher.
I'm really serious. I swear you young people sometimes.
https://en.wikipedia.org/wiki/WorldWideWeb
Here, email him yourself and ask away timbl [ a t ] w3.org
Hypertext links was simply the first step, but those existed for us for years before the web: gopher, specialty systems, etc.
A desire to move beyond those systems was part of what made the web work, and the first step was moving the web to graphical systems capable of displaying more than formatted fixed-width text on a VT100 terminal like some of the parents above think it was about. That's what gopher was for, that's not what the web was for.
It's both important and unimportant about what the web originally was, because just like I said earlier, the web is about documents as much as cars are about horses. The web has had javascript longer than the web only supported text and links. Think about that.
No it wasn't. The goal was to get documents that could be read by users no matter what software or computer they were using.
In this thread we're talking about a text document with some images. Javascript contributes nothing to the content. All Javascript is used for in this example is to put a fucking huge ad over the content before the content has loaded, and add some social media widgets. These detract from the content, and make the page harder to use.
again, where is this notion coming from? even if we scope to just text and no images, we already broken on this idea once we move beyond non-latin scripts and unicode.
But that's not the web, the web is not intended for lynx, it's intended for a browser, and all the foibles that browsers bring along with them.
Go rethink your position a bit, because maybe I'm old, but I remember the way the internet worked before the web and after the web, and "displaying documents suitable for a vt100 terminal" was not what the web was ever about.
From W3C and the like. I dunno, they built WWW, I guess they have some idea what their intentions were.
> even if we scope to just text and no images, we already broken on this idea once we move beyond non-latin scripts and unicode.
Just so we're clear about what my claims are: you don't need javascript for a simple text article with a few images. The submitted article is a simple text article, with a few images. Javascript is used only to make the experience worse.
You're wrong about images and about unicode - neither of those need javascript. I don't know why you mention vt100 terminals (why so redundant?) - that's not a point I'm making.
But since you brought it up a web dev has to be some kind of clueless cunt if they can't display a bit of text with image placeholders on a text mode display.
technical documentation includes information that can't be displayed on VT100 terminals and pretending like that's all the web is is clearly and obviously incorrect
I've started adding same to my default stylesheet as block elements.
This covers a lot of sins:
[class*="modal"], [class*="popup"], [class*="overlay"],
[class*="interstitial"], [class*="social"], [class*="cookie"],
[class*="flyout"], [class*="colorbox"], [class*="Modal"],
[class*="Popup"], [class*="Overlay"], [class*="Interstitial"],
[class*="Social"], [class*="Cookie"], [class*="Flyout"],
[class*="Colorbox"], [id*="modal"], [id*="popup"], [id*="overlay"],
[id*="interstitial"], [id*="social"], [id*="cookie"],
[id*="flyout"], [id*="colorbox"], [id*="Modal"], [id*="Popup"],
[id*="Overlay"], [id*="Interstitial"], [id*="Social"],
[id*="Cookie"], [id*="Flyout"], [id*="Colorbox"] {
display: none;
}