Normalize.css: Normalize blink and marquee

[SoniEx2]

Apparently those still work in chrome but not in firefox. It would be nice to use CSS3 animations to make them work everywhere.

[garrettw]

Oh goodness, surely we don't want to encourage _that_.

[Toddses]

Yea I don't imagine anyone will be normalizing obsolete html features. Frankly you shouldn't be using these in your code, Chrome will ultimately remove them. Your code should be as future-proof as possible - using <blink> ensures your code will ultimately break.

[SoniEx2]

Your code should be as future-proof as possible - using ensures your code will ultimately break.

not if normalize.css implements it in CSS. if I want my website to look the same in IE4 and Firefox 59, I need these. (or alternatively, if I want it the same in modern versions of chrome and firefox...)

[Toddses]

This is anathema to the purpose of normalize.css. If you want a future-proof version of <blink>, you should create a custom component. I don't speak for necolas, but I can basically guarantee he's not going to normalize obsolete HTML features.

Personally, and probably this means nothing to you, but I'd avoid using any type of blink for all but the rarest usecases. There's a reason it became an obsolete HTML feature.

[SoniEx2]

works on my text/terminal browser. CSS doesn't.

[EmmanuelBeziat]

There's a reason it became an obsolete HTML feature.

Those tags aren't obsolete HTML feature. Because they have never been part of any HTML version or spec. Ever. They've been introduced by Netscape (blink) and IE (marquee) as proprietary non-standard tags.

It's totally normal that it don't work in a modern browser, and it's a shame that Chrome support this.

https://www.w3.org/wiki/Html/Elements/marquee

No, really. don't use it.

https://www.w3.org/wiki/Html/Elements/blink

No, really, don't use it. It's simply evil.

So, no, this should not ever be put in normalize.css.

[SoniEx2]

please?

[garrettw]

please don't beg. he basically said no, so just let it die