Live data from Hacker News

and (2020)

danq.me

181–190 of 191 posts

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

#182

Earlier quoted context omitted.

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

Same here, but this is in spite is the governance of the foundation looking so out of rails and simultaneously lake of better alternative I'm aware of with both better governance and fine enough technological state.

Seamonkey is still out there. The rot hasn't touched the Seamonkey foundation, in part because only like, my dad uses, or has heard of, Seamonkey.

Seamonkey is pretty much the descendant of the OG Netscape Communicator codebase. So it's kind of on topic for retro Web stuff.

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

#183

Ahh, good times. I ran a "college dorm floor" website off my computer for a while and included a 997-word marquee on it, just rambling and talking about girls, depression, and philosophy. At the very end there was an exclamation point that was a href to a hidden page. Of course, someone hit view source to read the stupidly long message and found the page anyway.

Remember clicking on various places to uncover Easter eggs in Homestar Runner?

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

#184
post #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 count…

It's simple, really. You're not allowed into India if you've been to more than 20 countries in the last ten years. What are you trying to hide with all that globetrotting?

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

#185
post #137

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…

I browse Hacker News through a custom aggregator. This post is how I found out it’s susceptible to HTML injection - a (2020) was marqueeing across my screen.

Same here. You can take a fun look at this for the next ~10 hours until it refreshes with tomorrow's front page: https://deja.de.hueve.ar/hn

Also: I built the thing, so maybe I should fix it some time.

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

#186
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…

> Who here remembers frames?

I was there, writing sites professionally when this was rolled out.

They're more or less deprecated, but I missing having a 1st-class building block that allows you to resize areas of the screen. Recommendations are to use anything but a , but there's no replacement for that one feature.

https://html.com/frames/

> I remember building site navigations in Java, Flash, and Silverlight.

Don't forget ActiveX (actually, yes, we should all try to forget)

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

#188
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 wish I could upvote this comment twice. Thank you for the walk down memory lane.

I recall, in about 2010, hiring a young engineer to help with small marketing pages at an agency in New York City. His work was pixel-perfect at a time when we’d spend days just trying to get things looking reasonable in IE6. He was fast. It was incredible.

He was gone for the day when a last-minute change came in, so another dev went to update his latest work. Turns out he had been exporting the entire designs (from Photoshop, of course, no Sketch or Figma back then) as a BACKGROUND IMAGE and then ABSOLUTELY POSITIONING form fields.

I thought it was brilliant. No one else but the boss agreed. Testing for all of his work had been flawless cross-browser. It just didn’t work well on mobile. But he didn’t have to center things in a div - it was all smoke and mirrors.

I miss those days sometimes.

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

#189
post #73

Earlier quoted context omitted.

I developed web software with frames and I thought it was perfectly fine. To this day I still don't understand the issue with frames. People sometimes mention accessibility for screen readers, but nothing more specific than that, so I still don't know what the actual problem is.

> I still don't understand the issue with frames. I paid for 1024x768. Because of your frames, the content I'm actually interested in is now restricted to some disgusting and dismaying fraction of that. The borders of my bitchin' 15" CRT are now committed to navigation (which I have to scroll horizontally to actually make sense of) and what is likely a LinkExchange banner on the bottom that adds absolutely nothing to…

Hm, have you been on the web lately? I've got bad news for you.
Post reply on HN