3 ms·

<blink>Came here for deprecated attributes, but found an informative article.</blink>

ravenstine 5y ago
<marquee>Never forget the fun of the early web!</marquee> Yeah, I had the same cynical assumption before reading. All in all, I can't remember coming across a deprecated HTML feature that I needed and didn't already have a better alternative.
- 0des 5y ago
  Pouring one out for server side includes and my homie cgi-bin as we speak
  - extra88 5y ago
    I still have some web pages I update on a shared host that use server side includes to display the HTML file's last modified date.
  - matt_kantor 5y ago
    Those aren't part of HTML, rather features of web servers that are evaluated server-side. Furthermore I think you can still use this stuff. Apache and Lighttpd are still perfectly fine web servers depending on the use case. Also nginx supports server-side includes and fastCGI.
- bryanrasmussen 5y ago
  The xmp element worked better for its purpose than any of the replacing elements, in my experience, http://www.the-pope.com/listin.html http://www.the-pope.com/listin.html
- chrisfinazzo 5y ago
  I'm a bit surprised the autoplay attribute - at least how it's been used for <audio> and <video> hasn't been similarly consigned to the dustbin of history. What is taking so long? /s (Only a bit of sarcasm there, I actually would like to know...)
  - extra88 5y ago
    `autoplay` is rarely appropriate to use, but not never. If a link named "Play 'Never Gonna Give You Up'" goes to a page with <video autoplay …>, that's fine. If the user is informed that the action they're going to take will lead to audio or video playing, you don't have to make them click an additional thing (a "play" button) to make the content play.
- extra88 5y ago
  <blink> and <marquee> are HTML elements, the article is about HTML attributes. None of the attributes in the article are deprecated, some are underimplemented (alternative stylesheets).
  - mxuribe 5y ago
    The mischievous imp in me wanted to reply with something like the following: <blink speed="fast">how fast should this blink?</blink> ...But, then that's just not healthy for anyone. :-)
    - extra88 5y ago
      You got me, I actually searched for evidence that the <blink> element supported a `speed` attribute. The MDN page about <blink> has example CSS to make the element blink again. If you wanted to make speed variants, you could use CSS selectors that set different durations based on a data attribute and its value: blink { animation: 2s linear infinite condemned_blink_effect; } blink[data-speed: fast] { animation-duration: 1s } blink[data-speed: slow] { animation-duration: 4s }
      - mxuribe 5y ago
        Oh that's awesome!

<marquee>Never forget the fun of the early web!</marquee> Yeah, I had the same cynical assumption before reading. All in all, I can't remember coming across a deprecated HTML feature that I needed and didn't already have a better alternative.

0des 5y ago
Pouring one out for server side includes and my homie cgi-bin as we speak
- extra88 5y ago
  I still have some web pages I update on a shared host that use server side includes to display the HTML file's last modified date.
- matt_kantor 5y ago
  Those aren't part of HTML, rather features of web servers that are evaluated server-side. Furthermore I think you can still use this stuff. Apache and Lighttpd are still perfectly fine web servers depending on the use case. Also nginx supports server-side includes and fastCGI.
bryanrasmussen 5y ago
The xmp element worked better for its purpose than any of the replacing elements, in my experience, http://www.the-pope.com/listin.html http://www.the-pope.com/listin.html
chrisfinazzo 5y ago
I'm a bit surprised the autoplay attribute - at least how it's been used for <audio> and <video> hasn't been similarly consigned to the dustbin of history. What is taking so long? /s (Only a bit of sarcasm there, I actually would like to know...)
- extra88 5y ago
  `autoplay` is rarely appropriate to use, but not never. If a link named "Play 'Never Gonna Give You Up'" goes to a page with <video autoplay …>, that's fine. If the user is informed that the action they're going to take will lead to audio or video playing, you don't have to make them click an additional thing (a "play" button) to make the content play.
extra88 5y ago
<blink> and <marquee> are HTML elements, the article is about HTML attributes. None of the attributes in the article are deprecated, some are underimplemented (alternative stylesheets).
- mxuribe 5y ago
  The mischievous imp in me wanted to reply with something like the following: <blink speed="fast">how fast should this blink?</blink> ...But, then that's just not healthy for anyone. :-)
  - extra88 5y ago
    You got me, I actually searched for evidence that the <blink> element supported a `speed` attribute. The MDN page about <blink> has example CSS to make the element blink again. If you wanted to make speed variants, you could use CSS selectors that set different durations based on a data attribute and its value: blink { animation: 2s linear infinite condemned_blink_effect; } blink[data-speed: fast] { animation-duration: 1s } blink[data-speed: slow] { animation-duration: 4s }
    - mxuribe 5y ago
      Oh that's awesome!