Blink element

The blink element is a non-standard HTML element that indicates to a user agent (generally a web browser) that the page author intends the content of the element to blink (that is, alternate between being visible and invisible).[1] The element was introduced in Netscape Navigator[2] but is no longer supported and often ignored by modern Web browsers; some, such as Internet Explorer, never supported the element at all.[3]

Despite its initial popularity among home users in the 1990s, it fell out of favor due to its overuse and the difficulty it presents in reading.[4] Lou Montulli, often credited as the inventor of the blink element, claims he only suggested the idea, without writing any actual code.[5]

... At some point in the evening I mentioned that it was sad that Lynx was not going to be able to display many of the HTML extensions that we were proposing, I also pointed out that the only text style that Lynx could exploit given its environment was blinking text. We had a pretty good laugh at the thought of blinking text, and talked about blinking this and that and how absurd the whole thing would be. ... Saturday morning rolled around and I headed into the office only to find what else but, blinking text. It was on the screen blinking in all its glory, and in the browser. How could this be, you might ask? It turns out that one of the engineers liked my idea so much that he left the bar sometime past midnight, returned to the office and implemented the blink tag overnight. He was still there in the morning and quite proud of it.[5]

Usage

The blink element is non-standard, and as such there is no authoritative specification of its syntax or semantics. While Bert Bos of the World Wide Web Consortium has produced a Document Type Definition that includes syntax for the blink element (defining it as a phrase element on a par with elements for emphasis and citations), the comments in the DTD explain that it is intended as a joke.[6]

Syntax of the blink element type is identical to such standard HTML inline elements as span. For example: <blink>This text could blink</blink>. The rate of blinking is browser-specific, and the tag contains no parameters or means to adjust the rate of blinking. In versions of Mozilla Firefox that support the tag, the text alternates between being visible for three quarters of a second and being invisible for one quarter of a second.[7]

The blink element type was first invented for Netscape Navigator and was supported in its descendants, such as Mozilla Firefox (except for the Netscape 6 and early Mozilla suite browsers); it was removed in version 23.[8][9] Microsoft's Internet Explorer and WebKit (the browser engine behind Apple's Safari and Google Chrome) never supported it, even in its CSS incarnation. It was also supported by the Opera Internet Browser, but support ended in version 15 when that browser switched to a WebKit-based engine. Vivaldi, despite its roots as a spiritual successor to the Presto-based Opera, also does not support a functional blink tag.

Some software supports the blink element as an easter egg. Google Search blinks parts of the page when one searches for "blink html".[10] Android's user interface framework supports the blink tag, labeling it as TAG_1995 in its source code.[11]

Implementation

The blink value of the CSS text-decoration property allows authors to suggest that text should blink without using proprietary tags, but the CSS 2.1 Specification states that "conforming user agents may simply not blink the text" in order to comply with the User Agent Accessibility Guidelines.[12]

1 <span style="text-decoration: blink;">Text to blink here</span>

The blink element may also effectively be re-implemented using CSS animations.

 1 blink, .blink {
 2   -webkit-animation: blink 1s step-end infinite;
 3   -moz-animation: blink 1s step-end infinite;
 4   -o-animation: blink 1s step-end infinite;
 5   animation: blink 1s step-end infinite;
 6 }
 7 
 8 @-webkit-keyframes blink {
 9   67% { opacity: 0 }
10 }
11 
12 @-moz-keyframes blink {
13   67% { opacity: 0 }
14 }
15 
16 @-o-keyframes blink {
17   67% { opacity: 0 }
18 }
19 
20 @keyframes blink {
21   67% { opacity: 0 }
22 }

Similar effects can also be achieved through the use of JavaScript.

 1 <script type="text/javascript">
 2   (function() {
 3     var blinks = document.getElementsByTagName('blink');
 4     var visibility = 'hidden';
 5     window.setInterval(function() {
 6       for (var i = blinks.length - 1; i >= 0; i--) {
 7         blinks[i].style.visibility = visibility;
 8       }
 9       visibility = (visibility === 'visible') ? 'hidden' : 'visible';
10     }, 250);
11   })();
12 </script>
13 <blink>Text to blink here</blink>

Or alternatively, the blink functionality can be implemented with the help of jQuery.

1 <script type="text/javascript">
2     setInterval(function(){
3       $('blink').each(function() {
4         $(this).toggle();
5       });
6     }, 250);
7 </script>
8 <blink>Text to blink here</blink>

Usability and accessibility

A 1982 Apple Computer manual for developers advised against using blinking text, warning that "flashing [text] should only be used to indicate imminent destruction of data or the program".[13] The blink element has been consistently criticised by usability and accessibility experts. In 1996 Jakob Nielsen described the element as "simply evil" in his Alertbox column Top Ten Mistakes in Web Design.[14] The World Wide Web Consortium's Web Content Accessibility Guidelines (WCAG) 1.0 state that content authors should avoid causing the screen to flicker or blink, noting that such effects can cause problems for people with cognitive disabilities or photosensitive epilepsy.[15]

The United States Federal Government's Section 508 states that pages should avoid causing the screen to flicker with a frequency between 2 Hz and 55 Hz, a range that covers rapidly blinking text.[16]

The German Federal Government's Barrierefreie Informationstechnik-Verordnung (Accessible Information Technology Ordinance) also states that flickering or blinking content should be avoided.[17]

To comply with the User Agent Accessibility Guidelines a user agent must either "allow configuration to render animated or blinking text content as motionless, unblinking text" or never blink text.[18] Mozilla Firefox satisfied this requirement by providing a hidden configuration option to disable blinking,[7] browser.blink_allowed, which could be accessed through about:config. The blinking feature has been disabled altogether since version 23.[8]

gollark: Wait, maybe we should work out mods first.
gollark: 🌵 🇶
gollark: I still think that cactus cactus octobadger initiating protocol delta.
gollark: But this is more focused on combat.
gollark: I mean, players want to work in teams, sure, that makes sense, and good tooling for that is important.

See also

References
  1. "<blink>". Mozilla Developer Network. Retrieved 11 September 2017.
  2. "the origin of the <blink> tag - www". www.montulli.org. Retrieved 11 September 2017.
  3. "<blink>". Mozilla Developer Network. Retrieved 11 September 2017.
  4. "Saying Goodbye To The HTML Blink Tag". Fast Company. 7 August 2013. Retrieved 11 September 2017.
  5. "The Origins of the <blink> Tag". www.montulli.org. Retrieved 23 October 2009.
  6. Bos, Bert. "HTML40, but with BLINK added". World Wide Web Consortium. Retrieved 12 December 2006.
  7. "VPAT for Firefox 3.0 and 3.5". Mozilla. Retrieved 23 October 2009.
  8. "Firefox 23 Release Notes". 6 August 2013. Retrieved 8 August 2013.
  9. <blink> - HTML | MDN
  10. McNamara, Paul (24 February 2014). "Google Easter Egg Leads to Story Behind 'Blink' Tag". NetworkWorld.com. Network World. Retrieved 20 January 2015.
  11. "core/java/android/view/LayoutInflater.java - platform/frameworks/base - Git at Google". android.googlesource.com. Retrieved 20 September 2019.
  12. "Cascading Style Sheets, level 1". Cascading Style Sheets Working Group, World Wide Web Consortium. Retrieved 23 October 2009.
  13. Meyers, Joe; Tognazzini, Bruce (1982). Apple IIe Design Guidelines (PDF). Apple Computer. p. 38. Archived from the original (PDF) on 23 September 2015. Retrieved 11 March 2014.
  14. "Original Top Ten Mistakes in Web Design (Alertbox)". Useit.com. Retrieved 23 October 2009.
  15. Chisholm, Wendy; Vanderheiden, Gregg; Jacobs, Ian (5 May 1999). "Web Content Accessibility Guidelines 1.0". World Wide Web Consortium. Retrieved 20 July 2010.
  16. Government Services Administration. "Section 508: Section 508 Standards". Section508.gov. Archived from the original on 22 October 2009. Retrieved 23 October 2009.
  17. "BITV â€” Einzelnorm". gesetze-im-internet.de. 12 September 2011. Retrieved 3 March 2014.
  18. "2. The user agent accessibility guidelines". W3.org. 17 December 2002. Retrieved 23 October 2009.

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.