Live data from Hacker News

and (2020)

danq.me

61–70 of 191 posts

Re: <Blink> and <Marquee> (2020)

#61
post #29

The blink tag was, of course, much hated back in the day, so as an experiment, I took the binary of whatever browser I was using (Netscape, I guess), searched for "blink", and changed it to "blonk". Tada, no more blinking!

Yeah, but if someone had used you would get... blonking I guess? :) Nice hack!

Re: <Blink> and <Marquee> (2020)

#62
post #41

Earlier quoted context omitted.

I don't know, I still use Firefox as my primary browser.

Root for the illegal Google monopoly then, because that's what Mozilla says they need to survive. (It's over soon.)

I assume you were being sarcastic? I see it the other way around - the sooner Mozilla gets off the drugs^WGoogle's money the better the chance we get a proper competitor to Chrome.

Re: <Blink> and <Marquee> (2020)

#63
They took away the tag from us, due to what can only be explained as the high costs to maintain such a complex feature in modern browsers, and late stage capitalism.

However, thanks to the brilliant hard work of the open source community, we have a widely supported browser polyfill: https://github.com/yocontra/blink-polyfill

Re: <Blink> and <Marquee> (2020)

#64
post #21

I was there, 3,000 years ago. I remember fights over whether or not navigation in frames was bad practice. Not iframes, frames. Who here remembers frames? I remember using HTTP 204 before AJAX to send messages to the server without reloading the page. I remember building... image maps[1]... professionally in the early 2000. I remember spending multiple days drawing the borders of States on a map of the country in Dre…

I remember cgi.pm and the magic of communicating two ways.

Re: <Blink> and <Marquee> (2020)

#65

Lot of older India gov sites still seem to use these tags. https://www.epfindia.gov.in/site_en/index.php

I just applied for an evisa for India. It was horrendous. Pages wouldn’t continue without telling you what was wrong (too many or not enough commas in the address/phone field was one). When returning to the form the pre filled data had quotes in, which then wasn’t valid. Missing labels on fields. Then the hilarious “what countries in the last ten years, list all or get deported” combined with “you have too many countries”. They only allow 20.

I don’t know if it’s the state of development in the country as a whole or just the lowest bidder for a government service problem.

Re: <Blink> and <Marquee> (2020)

#66
post #21

I was there, 3,000 years ago. I remember fights over whether or not navigation in frames was bad practice. Not iframes, frames. Who here remembers frames? I remember using HTTP 204 before AJAX to send messages to the server without reloading the page. I remember building... image maps[1]... professionally in the early 2000. I remember spending multiple days drawing the borders of States on a map of the country in Dre…

I was expecting you to tell me that all of these moments will be lost in time, like tears in the rain.

Re: <Blink> and <Marquee> (2020)

#67
post #21

I was there, 3,000 years ago. I remember fights over whether or not navigation in frames was bad practice. Not iframes, frames. Who here remembers frames? I remember using HTTP 204 before AJAX to send messages to the server without reloading the page. I remember building... image maps[1]... professionally in the early 2000. I remember spending multiple days drawing the borders of States on a map of the country in Dre…

I remember when display flex was still new, experimental, and not universally supported :)

Re: <Blink> and <Marquee> (2020)

#68
I find marquee extremely useful, for one reason: HTML injection.

I find it helpful to test for HTML injection vulnerabilities because marquee moves, and it's a tag that (almost) nobody intentionally uses, making it easy to identify when an attack works.

I also find it helpful to show non-technical people the effects of HTML injection, because, again, it moves. "This moves and it really shouldn't move" is something people understand better than "this text is bold and it really shouldn't be bold."

Re: <Blink> and <Marquee> (2020)

#69

I find marquee extremely useful, for one reason: HTML injection. I find it helpful to test for HTML injection vulnerabilities because marquee moves, and it's a tag that (almost) nobody intentionally uses, making it easy to identify when an attack works. I also find it helpful to show non-technical people the effects of HTML injection, because, again, it moves. "This moves and it really shouldn't move" is something pe…

When doing HTML sanitization, I always whitelist marquee as an easter egg (and almost nothing else)

Re: <Blink> and <Marquee> (2020)

#70
post #41

Earlier quoted context omitted.

Root for the illegal Google monopoly then, because that's what Mozilla says they need to survive. (It's over soon.)

I assume you were being sarcastic? I see it the other way around - the sooner Mozilla gets off the drugs^WGoogle's money the better the chance we get a proper competitor to Chrome.

The opposite will happen as they lose most of their funding. They will have to fire most developers and switch to chromium, to become yet another Chrome reskin. Congratulations, you killed Firefox.
Post reply on HN