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

171–180 of 191 posts

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

#171

Post by freeone3000 »

torgoguys wrote: post #108
atesti wrote: post #91

Earlier quoted context omitted.

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…

They could! window.parent exists for this! Also, the target attribute on a.

For multipart frame targets, the fix then, as it is now, is to parse out the URL fragment params into something reasonable. SPAs use the path for state; no reason you couldn’t use it for frames.

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

#172

Post by rossant »

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…

Memories. Made my first website in 1998. In Notepad. I had fun with HTML but not many ideas about what I could create. So I learnt HTML by making, in HTML, an HTML tutorial website. I was 12.

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

#174

Post by rda2 »

Sophira wrote: post #163
rda2 wrote: post #137

Earlier quoted context omitted.

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.

This whole comment section must be absolutely hell to look at on that...

Ironically, it's a titles/links only aggregator. My way of browsing social media antisocially.

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

#175

Post by bwann »

Back in the ISP days of the 90s, if you used the Microsoft Internet Explorer Administration Kit (IEAK) and wanted to distribute customized versions of IE to your customers, one of the requirements was to use IE-only elements on your main website to promote usage of IE. Marquee was one of the least obnoxious ways to do that compared to other options.

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

#177

Post by bazoom42 »

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.

Frames had multiple UX issues. For example they didn’t work well with search engines. Since search engines indexed individual pages, the search result would link to the page without the framing. Some developers would counteract this with js contraptions which reloaded the frameset, usually losing the context and breaking the back-button.

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

#178

Post by andirk »

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…

I remember using the "Sliding Doors" technique.

https://www.htmlgoodies.com/css/how-to-create-sliding-doors-...

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

#179

Post by ddoeth »

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…

> Who here remembers frames?

Don't worry, they are still alive, the swedish crime statistics website still uses them [0]. It's a great experience for everyone.

[0]: https://statistik.bra.se/solwebb/action/index

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

#180

Post by llui85 »

InsideOutSanta wrote: post #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 pe…

I've always used the tag - an unclosable element that converts the rest of the document into raw HTML. It's very obvious.

https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/...

Post reply on HN