Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

and (2020)

danq.me

Post reply on HN
Print view View original

91–100 of 191 posts

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

#91

Post by atesti »

Timwi wrote: post #73
donatj wrote: 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 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.

If you right click a link and open in new window (or middle click), the frameset was gone and only the piece in the frame was visible. Also you could not bookmark anything. I remember doing a frameset per content frame url automatically and also redirecting to that frameset from inside the page via javascript if the content frame's url was directly opened.

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

#92

Post by arp242 »

dmatech wrote: post #90

The amusing thing is that even today, there's a "blink" method on JavaScript strings. It's totally useless today, but it's still there for whatever reason. In fact, they don't even HTML escape the argument, so they were arguably terrible from the beginning. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

Removing it will cause old code to throw an exception. By making it a no-op the code will remain working. There's tons of old unmaintained stuff on the web.

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

#93

Post by esprehn »

divbzero wrote: post #17

Interestingly, the default doesn’t appear as smooth as a CSS animation would be? Playing with the scroll speed makes it feel smoother: scroll faster than default

In Chromium it's quite literally a CSS animation: https://source.chromium.org/chromium/chromium/src/+/main:thi...

All the code in that file is a fun read. was rewritten as if it was a web component using the public DOM APIs (ex. It uses CSS animations and requestAnimationFrame).

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

#94

Post by trallnag »

shawn_w wrote: post #40
atemerev wrote: post #31

Earlier quoted context omitted.

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

I don't know how people can use anything else, especially now that Chrome doesn't support ad blockers.

It still supports stripped down as blockers. For the casual user something like ublock lite is probably perfectly fine

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

#96

Post by senfiaj »

satiric wrote: post #3

Considering the marquee tag works in basically all browsers [1], has anyone here actually found a good, unironic use for it in today's world of crazy CSS animations? [1]: https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/...

Perhaps better semantics?

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

#97

Post by layer8 »

rdrd wrote: post #84
donatj wrote: 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 working for a client who needed to support IE6 (with all the insane bugs/quirks/limitations) and I’d despair every time the designers would hand over a Photoshop design with rounded corners. They also needed it to be responsive (at the time mostly just different desktop sizes). Would usually require cutting the corners out and positioning them in table cells. There’s a certain amount of dev resilience you…

At least table rows didn't unexpectedly wrap to a new line like float-based layouts.

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

#98

Post by connorgurney »

donatj wrote: 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…

Oh, man, this takes me right back. Scary how time gets away from you.

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

#100

Post by HnUser12 »

chgs wrote: post #65
HnUser12 wrote: post #54

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…

All of that is true. However, to be fair, these are older sites. The newer ones are generally cleaner and usable[1]. Even the services provided is much more streamlined.

https://web.umang.gov.in/landing/

Post reply on HN