Why are hyperlinks blue?
blog.mozilla.org
blog.mozilla.org
Very strange that this article didn't bother to even consider or investigate this, simply dismissing the NeXT as monochrome.
See for example:
https://www.w3.org/History/1994/WWW/Journals/CACM/screensnap...
https://en.wikipedia.org/wiki/WorldWideWeb#/media/File:World...
Can you find a screenshot definitively from before 1993 that shows blue hyperlinks?
EDIT: as of 1991 (the earliest known code), it was still a black underline in the code. See line 640 of
https://github.com/cynthia/WorldWideWeb/blob/master/NextStep...
As of March 1991 he was contemplating providing color underlines, see line 61 here:
https://github.com/cynthia/WorldWideWeb/blob/master/NextStep...
Clearly it changed between 1991 and 1993 but I don't know when. Money still on WorldWideWeb.app being the first blue link application.
The oldest code I can find is here:
https://browsers.evolt.org/browsers/archive/worldwideweb/NeX...
WWWNextStep_0.15.tar.gz is dated 1993. It's imported here:
https://github.com/cynthia/WorldWideWeb/
Oh, but what is this:
https://github.com/cynthia/WorldWideWeb/blob/master/NextStep...
26 March 91 version 0.8
Changed anchor highlighting from dark grey to underline, now underline is available. (I may make underline &/or colour a user preference or style later.)
So we know that in March of 1991, links were underlined with a thought toward color in the future.
And here's the implementation:
https://github.com/cynthia/WorldWideWeb/blob/62b3c9b5082e455...
Which looks to me like it uses the default text color with the option to be changed via style:
https://github.com/cynthia/WorldWideWeb/blob/62b3c9b5082e455...
also was somewhat wondering if maybe the blue came from some sort of NeXT platform default. (grey #2 renders as blue on color machines or somesuch)
http://www.shawcomputing.net/resources/next/software/bundled...
Q: I'm a student of visual communications and asked myself why links are blue. I found some answers that might be, for example blue is a color of learning, but I'm not sure what is right. Is there any reason, why links are colored blue ?
A: There is no reason why one should use color, or blue, to signify links: it is just a default. I think the first WWW client (WorldWideWeb I wrote for the NeXT) used just underline to represent link, as it was a spare emphasis form which isn't used much in real documents. Blue came in as browsers went color - I don't remember which was the first to use blue. You can change the defaults in most browsers, and certainly in HTML documents, and of course with CSS style sheets. There are many examples of style sheets which use different colors.
My guess is that blue is the darkest color and so threatens the legibility least. I used green whenever I could in the early WWW design, for nature and because it is supposed to be relaxing. Robert Cailliau made the WWW icon in many colors but chose green as he had always seen W in his head as green.
One of the nicest link renditions was Dave Raggett's "Arena" browser which had a textured parchment background and embossed out the words of the link with a square apparently raised area.
[See also https://www.crazyegg.com/blog/why-hyperlinks-are-blue/ which links to the answer above but also contains a few other references.]
My intuition is that it comes from books/newspapers and nascent desktop publishing universes; sans-serif fonts being used for large amounts of body text anywhere, on paper or not, is relatively new as a mainstream thing. (That isn't to say it never happened, just that it's historically rare.)
This is why Apple makes Android users have white on green text, the least readable choice.
Green hyperlinks stuck around in the Windows 95 help system, and were eventually replaced when Windows 98 switched to Microsoft's new HTML Help system which defaulted to blue hyperlinks (inherited from Internet Explorer).
The timeline might undermine my assumption.
At any rate, there wouldn't be any need to distinguish internal help links from web links, because neither Windows 3.0 nor 3.1 ever shipped with a web browser-- can't link out in your docs if the tools aren't available to follow the links. Early versions of Windows 95 didn't, either, with IE 2.0 being bundled with the OS for the first time with OSR1.
Something the article doesn't touch on is the fact that there wasn't really such a thing as hex colors like "#0000ff" back then. You could use them, but no one did because they weren't guaranteed to work properly. There was a list of 256 "web safe colors" that you could use that were the 8 bit palette that most computers supported in VGA graphics (at 640x480 resolution), and then a further list of HTML colors that could be used if the user had a graphics card that could use 16 bit SVGA graphics. Using 24 bit hex code colors didn't come along until a little later, when computers were likely to display them properly.
In other words, links weren't #0000ff. They were "blue".
I think some browsers understood X11 color names like "blue" or "DarkSlateGray", but there are more than 216 of those, so same caveat applies.
This still exists in some weird places. For example, I have a Hue portable light that connects to Alexa and can change colors. But I can only tell it X11 color names...it doesn't understand anything else. Which is funny given that both devices are fairly modern.
You could use names, or you could use colors whose RGB components were each multiples of 0x33. (00, 33, 66, 99, cc, ff)
Web-Safe Colors (a Color Cube)
https://www.peachpit.com/articles/article.aspx?p=23671&seqNu...
Not to be confused with a Time Cube.
There were plenty of us who surfed the web in less than VGA. I was on monochrome.
OS/2 Warp had a web browser and supported CGA: https://www.mit.edu/activities/os2/faq/os2faq0201.html
That also led to interesting things like websites telling you how to calibrate your monitor so that they'd render correctly, e.g. http://sasg.com/help.html .
"anchorColor: color Color to shade anchors whose corresponding documents haven't been previously visited. Default is blue3.
visitedAnchorColor: color Color to shade anchors whose corresponding documents have been previously visited. Default is violetred4."
https://www.math.utah.edu/~beebe/support/html/Docs/resources...
In reverse order:
* Not all colors lent themselves equally well to a CRT, especially to the more cost effective ones. Green, esp. when in multiple shades, didn't render well (or, the other way round, issues with green are more easily detected by the human eye), so you won't see much green in early color UIs (or rather bright single-color expressions in elements like bars).
* Also, CRT specific, you want to stick with primary colors (RGB), since even a small misalignment of the cathodes will result in blurry text in more evenly distributed hues. (Same is true for the outer regions of larger color CRTs with shadow masks.)
* Monitor calibration wasn't always the best, shades of grey often exhibited a red hue, esp. on systems with a gamma of 2.0.
* Considering what we have established, we are searching for a color which consists mostly of R, G, or B and renders well on an average color CRT on top of a grey background of #C0C0C0. (Also, mind that in 1993/4, we're probably not speaking of millions of colors to choose from, but rather more of a 4-bit color palette, if we're looking for robustness.)
- Green, as already established, is somewhat complicated. Also, a mostly green color of comparable intensity is perceived somewhat brighter than, say a blue one. It will stand out against black text, probably more than you want, and it's contrast ratio to a light grey suffering from a red tint isn't great.
- Red may not be the best choice either, as its contrast to grey isn't the best (ask your printer) – and its use may be best reserved for representing an active state. (There's also the cultural issue with red usually signifying limits or even off-limit areas, which isn't especially inviting.)
- Which leaves blue for a passive state, which is actually a good choice. It's perceived slightly darker than the other primary colors, which is favorable for rendering text, it has a good contrast against light grey, and isn't affected by any missalignments or color calibration issues (as it doesn't share with red), and, while visible, isn't too distracting in what is mostly black text (you still want to provide for fluent reading of a given text, even, if it embeds a link). Moreover, it is more friendly to impaired vision than green or red (which are actually used in diagnosing defective vision). Properties, for which it had been used as a favorite color in UIs already. Moreover, on the cultural side of things, where red indicates restriction, blue indicates recommendation and instruction (compare traffic signs).
So, I think, blue was quite a natural choice.
A: There is no reason why one should use color, or blue, to signify links: it is just a default. I think the first WWW client (WorldWideWeb I wrote for the NeXT) used just underline to represent link, as it was a spare emphasis form which isn't used much in real documents. Blue came in as browsers went color - I don't remember which was the first to use blue. You can change the defaults in most browsers, and certainly in HTML documents, and of course with CSS style sheets. There are many examples of style sheets which use different colors.
My guess is that blue is the darkest color and so threatens the legibility least. I used green whenever I could in the early WWW design, for nature and because it is supposed to be relaxing. Robert Cailliau made the WWW icon in many colors but chose green as he had always seen W in his head as green.
One of the nicest link renditions was Dave Raggett's "Arena" browser which had a textured parchment background and embossed out the words of the link with a square apparently raised area.
- WorldWideWeb was not created in 1987. Tim Berners-Lee released it in December 1990, based on a proposal he developed in 1989 [1].
- Windows 1.0 in 1985 did not have hyperlinks. It also did not have overlapping windows. [2] That second screenshot is of Windows 2, (from December 1987) showing the "Help" system, which did use underlined hyperlinks, from 1989.
It makes me question the thoroughness of their research at all.
> What happened in 1993 to suddenly make hyperlinks blue? No one knows, but I have some theories. ... I like to imagine that Cello and Mosaic were both inspired by the same trends happening in user interface design at the time. My theory is that Windows 3.1 had just come out.
What? No! These are grad students working at the National Center for Supercomputing Applications in the 1990s on big powerful Unix workstations [3]. I highly doubt the UI choices of Window 3 were relevant or closely watched by that team.
1- https://en.wikipedia.org/wiki/Tim_Berners-Lee#Career_and_res...
2- https://www.filfre.net/2018/07/doing-windows-part-3-a-pair-o...
3- https://en.wikipedia.org/wiki/Mosaic_(web_browser)#History
Yeah. All you need to know about this article.
Monochrome monitors were often either green or amber or white. If the monitor used P1 Phosphor, then it was green, P3 Phosphor was amber, and P4 Phosphor was white. So the color of the text on the screen was a reflection of the hardware spec/design, not of the software.
You're probably right. I still struggle with tone sometimes. I'm still getting used to this whole "Internet" thing... ;-)
Check standard phosphor types section here: https://en.m.wikipedia.org/wiki/Phosphor
[1] https://en.wikipedia.org/wiki/Phosphor#Standard_phosphor_typ...
You wouldn't want that in a computer monitor. The computer is perfectly capable of refreshing the monitor, and the long duration of the phosphor would make anything rapidly changing (like a scrolling display) impossible to read because all of the previous contents would interfere with the current image.
---
1. Well really my second. The first was a Spectravideo computer I got for writing demo programs for the midwest distributor when I was in high school. It wasn't very useful though.
Why the hell were our monochrome displays not all white. What's the purpose of adding a color.
I grew up with MS-DOS and 4M of RAM, perhaps I should make a tiny VM with Windows 3.11 and Netscape to revisit these days and try to get my Jekyll blog running on it (served from CERN httpd or the popular webserver at the time). Not sure if VirtualBox virtual network adapter can be recognized by Windows 3.11. Perhaps someone can backport a Gemini browser to Windows 3.11.. perhaps someone can backport a modern WWW browser to Windows 3.11!
edit: someone provided VM's already! Just 33M for DOS622+WIN311 (but still a lot of floppies). I disabled the default USB support and the startup to GUI is ~5s. EDIT.COM has a "hypertext" links in it consisting of 2 little green arrows, 1 triangle rotated left on the left side and 1 right on the right side. The grey on black text is not underlined. http://virtualdiskimages.weebly.com/virtualbox.html
I mean who has the time to deep dive into 100% historical accuracy of these things.
I thought it was a neat look at a historical context of something mundane like a hyperlink.
I strongly disagree with this premise, there are plenty of people out there taking the past seriously and "full-assing" it.
So now this piece of crap is out there on the internet for the rest of time, permanently memorializing completely nonfactual statements. Fake news. Literal definition of. Wonderful.
You could fit a lot more OS on an HD in 1993 than you can now!
https://www.technologytips.com/windows-system-requirements/
At 64 MB, you wouldn't have a whole lot of space for data and applications / utilities, but you could certainly cram a couple of OSes on it.
The first "user-installable" linux was arguably SLS, which came on 24 1.5 MB floppies. I'm unsure what the installed size was, but likely in the 24 -- 48 MB range.
I remember downloading and compiling kernel 1.1 or 1.2 - which were released in 1994. In 1995 I bought the offical RedHat CD's, I might have tried Slackware or Debian floppy disks earlier. A friend was running Linux with X-Windows, Emacs and Mosaic on his Pentium with WindowMaker or AfterStep. No dual-boot. He was on usenet (with the built-in netscape usenet reader) and played with Lisp, he had studied physics (or was it philosophy) at the Utrecht University. Heaps of Byte and Astronomy magazines and SF books littered in his room where he enjoyed a glass of wine and a cigar. I occasionally dropped by for a chat about linux, SF, astronomy and the meaning of life and my own troubles. I think he had dropped out of college for some reason years ago but I never dared asking why. He was brilliant and stayed in the student dorm as a senior. Unfortunately at 45 or so he died in his sleep I heard later when I wasn't living there anymore. He had a good job at the municipality and was well respected for his knowledge, seriousness, dry and dark humor and wit and was still living in the student dorm.
This just isn't true.
We had "labs" with about 30 Windows/DOS PCs in them that were for general use (meaning word-processing). Probably 1 in 100 students had their own computer (and if so it was more likely to be an Amiga or Atari ST).
My course wasn't computer-related, but I took a few computer-based modules (graphics, vision, AI, intro to programming). All of these apart from intro to programming where done on university SunOS/Solaris or Irix machines (and Intro to Programming was in Turbo Pascal for DOS on those Windows machines).
The SGI Irix machines (made famous in the original Jurassic Park) were really nice.
That sentence would be "I have literally no idea, it seems completely arbitrary." There really isn't any value worth preserving, it's just misinformed commentary on a bunch of screenshots taken while the author was probably in diapers.
(a/k/a Cunningham's Law)
> Here Microsoft uses the “hyperlink blue” for active states when a user clicks on different drives, folders and icons.
Hyperlink blue was a much brighter blue (pure blue, on the interfaces I used, but I was a litter later in the timeline) than Window's blue, which was a (noticeably) darker blue.
This is what it looked like: http://toastytech.com/guis/win30help.png
No Blue Scotsman!
Tim Berners-Lee told Ben Shneiderman at the time that he was influenced by the design of the HyperTIES-based "Hypertext on Hypertext" project from the 1987 HyperText conference that the ACM published, which had light blue links.
https://news.ycombinator.com/item?id=28317104
>My students conducted more than a dozen experiments (unpublished) on different ways of highlighting and selection using current screens, e.g. green screens only permitted, bold, underscore, blinking, and I think italic(???). When we had a color screen we tried different color highlighted links. While red made the links easier to spot, user comprehension and recollection of the content declined. We chose the light blue, which Tim adopted.
>His systems with embedded menus (or hot spots), where a significant user interface improvement over early systems such as Gopher. But Tim told me at the time that he was influenced by our design as he saw it in the Hypertext on Hypertext project that we used Hyperties to build for the July 1988 CACM that held the articles from the July 1987 Hypertext conference at the University of North Carolina. The ACM sold 4000 copies of our Hypertext on Hypertext disks.
> Apple brought color to its HyperCards, but notably, the text links were still black and not blue.
HyperCard never natively supported any form of "text links". You could make a button with a text label, or a transparent button hovering over text, but there was no way to attach a behavior to a span of styled text without a lot of custom scripting.
(And, for what it's worth, the color XCMD for HyperCard never really caught on. It was a late addition, and never felt entirely like a native part of the application. Even when it was available, most users kept on authoring stacks in black and white.)
> However, some UI elements did have blue accents when interacted upon
I have no idea what the author is referring to here. Possibly the blue tint in the system UI (like window titlebars), which has nothing to do with HyperCard and didn't apply to its in-app UI?
I get the impression that the author was trying to answer two questions, the second being: where did the color blue come from?
I was also under the impression that the color XCMD was not a part of HyperCard and was created by a third party, but I could be wrong there since it has been over 20 years since I've used HyperCard.
The window tint in System 7 was a user preference. The purplish blue seen in the screenshot was the default color, but there were about a dozen other options. In any event, it seems a stretch to assume that Apple's choice of this color influenced Mosaic in choosing a different blue color for a different purpose.
Actually Windows 1.0 did have overlapping windows.
They just weren't the default style for application windows.
But there were popup windows that overlapped other windows on the screen. These were typically used for dialog and message boxes, for example the End Session message box midway through that filfre.net article.
There was nothing stopping anyone from using a popup-style window for their application, and adding a titlebar so you could move it around on the screen. It just wasn't the custom, and people would think your app was weird if it did that. And on a typical system of the day (no GPU!), dragging your window around on the screen would perform rather poorly.
I had read that Digital Antiquarian piece a few months back and had remembered about the "sub windows" that an app could have. But I had thought they were scoped to just be on top of the window for the app that spawned it, and couldn't leave that "tile."
However, you are totally right. This image right here clearly shows it overlapping another application's tiled window.
https://www.filfre.net/2018/07/doing-windows-part-3-a-pair-o...
This is the best kind of correct: technically correct!
WorldWideWeb was created by (mostly Republican) computer engineers who broke from IBM in Silicon Valley in the 1980s, forming little democratic circles of twenty to forty people with their laptops in each other's garages.
This looks simpler than listing a bunch of other UI, many non influential and none of them giving the answer.
Websites back then did not have white backgrounds, they were all gray. In fact I’ve always wondered why the default background was gray more than why the links were blue.
A white background in this situation could lead to noticeable flicker, especially as you moved your eyes, e.g. look away from the monitor and look back at it.
The gray background made this flicker less noticeable.
It's basically a tour of old hyperlink and windowing systems... with lots of guessing and maybes. I'm not sure why it's relevant that Win 3.1 had blue titlebars, for instance. The author never actually answers her question but I imagine the obvious guess is the correct one:
Black text on a white background was the predominant GUI style at the time (probably due to Mac OS and Windows) and the software designers needed a visual cue that the hyperlink was clickable. Just underlined wouldn't have worked because underline was already a popular style in text processing. So they decided to give it a different color too. Blue is the most logical choice as it has good contrast against a white background, and has a neutral meaning (compared to say, red). There weren't really a lot of color choices back then, the largest palette you could count on at the time was 16 colors.
This was what Mosaic did and most browsers that came after it (including the most influential: Netscape) did what Mosaic did.
And there certainly were browsers of the era that didn't use blue underline for links, the next most common paradigm was some kind of bordered box around the text (usually the same color as the text).
For a comment complaining about unsubstantiated speculation this struck me as exactly that…
https://en.wikipedia.org/wiki/ViolaWWW https://en.wikipedia.org/wiki/Mosaic_(web_browser) https://en.wikipedia.org/wiki/Internet_Explorer_2 https://en.wikipedia.org/wiki/Netscape_Navigator
In particular, notice the IE2 screenshot, which shows it displaying the more modern Wikipedia website using a gray background. IE2 doesn't understand CSS, so just displays the source. The CSS declares a white background, so we can infer that the HTML probably does not declare a gray background using the long forgotten BODY tag BGCOLOR attribute. (Rather, almost certainly the HTML doesn't use the BGCOLOR attribute at all.)
It's possible that Mosaic defaulted to white on Mac OS, but I doubt it. Netscape didn't back then, IIRC.
For a long time gray and gray-toned backgrounds were ubiquitous on the web. It was nice because white backgrounds are difficult on the eyes, especially for prolonged periods. Unfortunately, white eventually began to dominate, as it already did for most Windows and Mac applications. Now we're coming full circle with dark theming, though dark theming is typically much darker than the old web and old X applications.
Ben likes to actually run controlled experiments and measure things like that, instead of just speculating! ;)
See the email quoted here:
What are these comments? "Nice word choice" "No changes here" "This is perfect" "(smiley face)"
EDIT: Also used for printing instructions, to make sure that things come out in the right order, for instance.
You put the page with the correct word underneath the copy, on a light table (a real one). With an exacto knife, carefully cut out the word, cutting through both sheets. Now the correct word fits exactly in the hole. Hold it together with a piece of white tape (standard supply in all these shops) on the back. The mend is invisible.
But it is two browsers that chose blue, so perhaps there is some underlying Unix-y reason. Maybe early ncurses had chosen that blue for something unrelated to the web, and the decision goes back further.
Or maybe it was just lack of choices. For example, of the 16 original hex colors, blue & purple IMHO look the least like crap when mixed in with black text. Maybe its just that simple? red is too alarming, green is too bright, yellow/magenta/cyan/grey are too hard to read... now I'm speculating, but I think the answer might be an unrelated pattern in some other color-related origin.
That would explain whatever happened to Firefox.
Shameless plug: If anyone is looking to get rid of Chrome but don't like Firefox for any reason, try Brave, it is a great browser, really.
Mozilla amazes me with their org-bloat-to-products-they-sell-for-money ratio. They have programming language teams, research bloggers, occasional splashy products, an in-house bug tracker, and oh yeah, they make a web browser.
I don't know how they do it, but it seems to be working out for them. If I was the CEO of a company that only had one customer, I would probably not be hiring software engineers to write a programming language that's not even used for the core product. But, I guess that's why nobody ever asks me to be the CEO of a company!
Rust is used in Firefox
Having lived through the 80s with computers and owning a Commodore 1084 I'd say most had color much earlier.
I remember using the ViolaWww browser on a color XTerminal in 1992.
[1] https://stackoverflow.com/questions/55696808/why-do-h5-and-h...
I remember also, in the 90s, was quite popular yellow text against a black/dark blue background. The old days!
It used to be any visited link would look visited, regardless of the website. This made it possible to see where a user had visited across the web, and so visited links only apply to the current origin now.
At some point it also became hip to remove the underline from links, and links rarely have underlines anymore.
I'm assuming a JS query can check link status and colour? With a targeted or crafted link-of-interest, user activity might then be tracked, yes?
https://www.math.utah.edu/~beebe/support/html/Docs/resources...
anchorColor: color Color to shade anchors whose corresponding documents haven't been previously visited. Default is blue3.
visitedAnchorColor: color Color to shade anchors whose corresponding documents have been previously visited. Default is violetred4.
activeAnchorFG: color Color to shade anchors that are in the process of being activated. Default is red.
activeAnchorBG: color Color to shade the background of anchors that are in the process of being activated. Default is grey80 (the same color as the application's background).
That's just the docs for Mosaic which TFA says was responsible.
I'm confused, what in Windows 1.0 is, or is being called, a "hyperlink" that's underlined? Is it shown in the screenshots? I wouldn't have expected there would be such thing as a "hyperlink" in Windows 1.0, and am not sure what the author is referring to.
(Edited for tone.)
What does this superset/subset relationship refer to? I thought link was just a shortened word meaning the same as hyperlink.
These would have been provided through ANSI escape sequences, which allowed for white, black, red, green, blue, yellow, magenta, and cyan.
https://en.wikipedia.org/wiki/ANSI_escape_code
With a bright background (white), blue is the most clearly-visible non-black colour, and avoids R-G colourblindness issues. On a dark background (black), cyan is light enough to be readable, but not as glaringly distracting as either red or yellow.
Given the prevalence of green and amber phosphor displays, and some adoption of that colour scheme for terminal colours, yellow and green might have been avoided due to conflicts with standard text.
The next question is when colour support was added to terminals. I'm confident that xterm could have foreground/background colours specified by 1997. Support for 16 colours didn't hit xterm until 1996:
https://invisible-island.net/xterm/xterm.log.html#xterm_39
rxvt may have had colour support earlier. I'm unsure of dates or changelogs though it's mentioned in print as of 1994: https://www.google.com/books/edition/The_X_Resource/RKhFAQAA...
Also here's a link to an article about the NeWS version of HyperTIES that we developed at HCIL, and some demos of HyperTIES and its Emacs based authoring tool, which had pie menus and embedded interactive PostScript "applets" in 1988.
https://medium.com/@donhopkins/designing-to-facilitate-brows...
HCIL Demo - HyperTIES Browsing
https://www.youtube.com/watch?v=fZi4gUjaGAM&ab_channel=DonHo...
HCIL Demo - HyperTIES Authoring with UniPress Emacs on NeWS
https://www.youtube.com/watch?v=hhmU2B79EDU&ab_channel=DonHo...
Don Hopkins and pie menus in ~ Spring 1989 on a Sun Workstation, running the NEWS operating system.
https://www.youtube.com/watch?v=8Fne3j7cWzg&ab_channel=Cathe...
John Gilmore via Internet-history <internet-history@elists.isoc.org> Date: Mon, Apr 13, 2020, 11:56 PM To: Brian, internet-history, Jeff
I forwarded this question to my friend Don Hopkins, who was a student of Ben Shneiderman back in the day. Ben ultimately responded:
From: Ben Shneiderman <ben@cs.umd.edu> To: Don Hopkins <don@donhopkins.com> CC: John Gilmore <gnu@toad.com>, Ben Shneiderman <ben@cs.umd.edu> Subject: RE: [ih] origins of the term "hyperlink" Date: Mon, 13 Apr 2020 15:15:52 +0000
HI Don (and Jack Gilmore),
Thanks for including me in this conversation.
I do not have a claim for the term “hyperlinks” and don’t know when it came into use. My claim is for the visual interface for showing highlighted selectable links embedded in paragraphs. This is what we called embedded menu items in that I think is an influential paper on the topic, which was peer-reviewed and published in the CACM in April 1986.
https://dl.acm.org/doi/10.1145/5684.5687
http://www.cs.umd.edu/~ben/papers/Koved1986Embedded.pdf
While Engelbart had shown a list that could be selected by pointing and clicking in 1968, I claim the idea of embedded highlighted selectable text in paragraphs. This was implemented by grad student Daniel Ostroff and described in:
Ewing J, Mehrabanzad S, Sheck S, Ostroff D and Shneiderman B (1986), "An experimental comparison of a mouse and arrow-jump keys for an interactive encyclopedia", International Journal of Man-Machine Studies, Jan., 1986, Vol 24, pp. 29-45.
[Abstract] [BibTeX] [DOI]
Ostroff D and Shneiderman B (1988), "Selection devices for users of an electronic encyclopedia: an empirical comparison of four possibilities", Information Processing and Management, Nov., 1988, Vol 24(6), pp. 665-680.
[Abstract] [BibTeX] [DOI]
I think the 1988 paper was the earlier study, but the publication took a while.
My students conducted more than a dozen experiments (unpublished) on different ways of highlighting and selection using current screens, e.g. green screens only permitted, bold, underscore, blinking, and I think italic(???). When we had a color screen we tried different color highlighted links. While red made the links easier to spot, user comprehension and recollection of the content declined. We chose the light blue, which Tim adopted.
His systems with embedded menus (or hot spots), where a significant user interface improvement over early systems such as Gopher. But Tim told me at the time that he was influenced by our design as he saw it in the Hypertext on Hypertext project that we used Hyperties to build for the July 1988 CACM that held the articles from the July 1987 Hypertext conference at the University of North Carolina. The ACM sold 4000 copies of our Hypertext on Hypertext disks.
Our history is here:
https://www.cs.umd.edu/hcil/hyperties/
and the video is very helpful in showing the design we used, which is what I think Tim built on for his WWW prototypes.
https://www.youtube.com/watch?v=29b4O2xxeqg
So in summary, I don’t know who coined hypertext, but I do think our work visual and interaction design was influential.
Our Hyperties system was picked up by Cognetics Corporation (around 1987) who made a modestly successful commercial run with it, doing dozens of corporate projects, most notably the Hewlett-Packard user manual for their Laserjet 4 was distributed as a Hyperties disk.
Hyperties was the name we shifted to after we got a stop and desist order from a lawyer because our TIES (The Interactive Encyclopedia System) conflicted with an existing product. By then “hyper” was a growing term.
Let me know if this helps, and what other questions you have…. Ben
Also, cyan is a much better color for text on a black background. Dark blue is almost invisible. This makes some of the early examples a little complicated since we moved to white backgrounds around the same time as the web came to fruition.
‘We’? Document-oriented workstations, including the one WWW was developed on, routinely used black-on-white back to the Alto, or NLS. (CAD stayed white-on-black due to the history of vector displays.)
Press [SPACE] for next screen, or as it was commonly known, "Spank the blank."
[G] for the document repository. Or as it was commonly called "G-Philes."
I also used the something-folio hypertext system before I used hypertext on the web. Did it have blue links? I can't remember.
I remember learning these with the LoVe / HAte mnemonic for CSS. Maybe from Cameron Moll, can't remember...
Similar to the reason to use yellow for highlighter and otherwise for changing the background color, you want a light color whose hue is detectable, but it similar enough to the white background that text is still easy to read.
The Munsell color solid is distorted to show that pure yellow is light, pure blue is dark.
https://art-design-glossary.musabi.ac.jp/wpwp/wp-content/upl...
Yes. If you were handed a printout or photo copy in 1980s with some terms or phrases manually marked to stand out, it was probably with blue underlines. Black didn’t stand out, red was for corrections.
That simple.
1: https://www.fastcompany.com/90669062/is-your-brand-on-mute-w...
2: https://stackoverflow.com/questions/24691460/how-does-wired-...
I doubt that no one knows. They found the smoking gun in the Mosaic release notes - the people who worked there are probably still alive and might remember why!
Let’s look at the primary and secondary colours.
Yellow: Bad contrast. Red or Green: Action colours, would be bad to see them everywhere. Plus there might be accessibility concerns. Orange: Mostly used as “Not as urgent as red”. Purple: Not as neutral as blue, yet it is the second best option, that’s why visited hyperlinks are purple I assume. It is the logical choice.
We are left with the colour blue. Also, a plus that it is a primary colour; I would assume it is easier to display primary colours in earlier tech.
In the future when augmented reality becomes the norm, it could be possible that clicking this blue link actually brings up a webpage, either on my phone, or broadcasted into my retina.
QR codes just don't cut it.
So blue was in the air by then.
It was actually a very good browser. Not as many features as Netscape but it was very fast. Netscape added too many fluff features like backgrounds and moving GIFs which were abused way too much (see any "1990s retro web site" for what I mean), so I often opted to using Mosaic even after Netscape became mainstream.
It makes sense too, black doesn't stand out enough from unlinked text. And can be confused with regular non-link underlining. It could have been any colour but it's a good convention. After all we could also have used green for stop and red for go (like in the first episode of "Sliders" :) ), but at least everyone around the world uses the same.
including the shortcuts on your desktop (which now functioned with a single click)
it was awful
(DoJ had some thoughts on that.)
Agree in general, but I wonder if a separate style for visited hyperlinks is still useful these days? Does anyone benefit by visited links being differentiated (by colour or another means) from unvisited ones?
Bootstrap is a good tool for CSS, but I think it also over-legitimzed restyling and reinventing native HTML interactive elements.
(Starman learns much like ML apparently.)