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

101–110 of 191 posts

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

#101

Post by layer8 »

8n4vidtmkvmk wrote: post #13
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/...

Plex does something very similar to marquee to display an actors name when it's too long to fit under their profile pic. Seems like a good use.

Music players, including car radios and portable CD and MiniDisc players, did that around 25 years ago. It's sort-of a standard UI pattern for variable-length text in a fixed-size display.

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

#102

Post by jabo »

The day I discovered that marquee tags have a direction attribute, using which you can make the text go up/down left/right and use multiple of these tags, is still etched in my memory.

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

#103

Post by al_borland »

ajdude wrote: post #49

I created this a while ago, and whenever I show someone they are shocked to see there is absolutely no JavaScript; all of the animations are done via marquee tags: https://udel.edu/~ianozi/

I probably haven't looked at the marquee tag in 20 years, so I could have just forgotten, but I was unaware it has a direction parameter to allow for vertical scrolling.

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

#104

Post by echelon »

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.

We should have frozen the web from 2006 - 2010 or so.

We had Ajax, lots of modern CSS, but weren't hell-bent on CSSifying and "SPA"-ing everything. Web standards hadn't yet jumped the shark.

It's also before Steve Jobs murdered Flash.

Killing Flash was one of the biggest mistakes we've made. The modern HTML/CSS/JS stack can't replicate how simple and functional it was. We're easily dealing with 100x the complexity now.

We let Google trick us into going down this path. And now they're going to kill the web to keep us on their LLMs and platforms.

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

#106

Post by al_borland »

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…

This was to prepare you for navigating once there. I still have flashbacks to the Delhi Airport. Every time I turned a corner there was someone there asking to see the name on my itinerary (a random sheet of paper I printed out hat I didn't think I'd actually need) with my passport and ticket. It happened so many times I almost missed my layover.

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

#107

Post by shortrounddev2 »

echelon wrote: post #104
Timwi wrote: 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.

We should have frozen the web from 2006 - 2010 or so. We had Ajax, lots of modern CSS, but weren't hell-bent on CSSifying and "SPA"-ing everything. Web standards hadn't yet jumped the shark. It's also before Steve Jobs murdered Flash. Killing Flash was one of the biggest mistakes we've made. The modern HTML/CSS/JS stack can't replicate how simple and functional it was. We're easily dealing with 100x the complexity no…

I agree. Personally I think we'd be better off without social media sites or smart phones

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

#108

Post by torgoguys »

atesti wrote: post #91
Timwi wrote: 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.

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.

Framesets were great.

>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.

Feature, not bug in my book. Same thing happens in today's iframes. But for situations where that is a problem, the spec could have been extended to support every page being able to identify a preferred parent frame. Or browsers could have changed behavior to by default duplicate a frame's parent and siblings when opening a frame in a new window.

>Also you could not bookmark anything.

Again a limitation of the spec that could have been addressed rather than throwing out a useful feature. We support have text fragment identifiers in URLs these days; surely we could have supported URLs with multipart frame targets.

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

#109

Post by rdrd »

layer8 wrote: post #97
rdrd wrote: post #84

Earlier quoted context omitted.

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.

Even though it was a long time ago I still have IE6/7 workarounds burned into my brain, most of them float related but also having a whole stylesheet for that damn browser... :

https://code.google.com/archive/p/universal-ie6-css/

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

#110

Post by bonoboTP »

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.

Currently you can still reactivate the ad blocker extensions, it's a bit hidden behind a three dot menu and you have to confirm a scary warning but it's still possible to run u lock origin at the moment. They might disable the workaround later though.
Post reply on HN