News for hackers. Stuff that matters.
Re:<Blink> and <Marquee> (2020) by xnx on Sunday June 08, 2025 @05:43AM (#44215853)
All content on the web should have a unique, linkable, URL. Frameset breaks that.
Re:<Blink> and <Marquee> (2020) by theandrewbailey on Sunday June 08, 2025 @06:32AM (#44216047)
That doesn't stop today's dynamically updating pages that also break the back button.
Re:<Blink> and <Marquee> (2020) by roryirvine on Sunday June 08, 2025 @10:06AM (#44217105)
Frames also broke the back button when they were first introduced!

Together with the other early problems - ugly borders, proliferation of scrollbars, and limited browser compatibility - it meant that frames were seen as a usability disaster right from the start.

They never managed to fully shake that reputation even as browsers improved in the later 90s.

Re:<Blink> and <Marquee> (2020) by ComplexSystems on Sunday June 08, 2025 @11:02AM (#44217426)
That ship has long since sailed. We live in a world of web apps with dynamically created content, AJAX, and so on. The main entry point for the app has a URL, and then within the app all bets are off. Same with framesets.
Re:<Blink> and <Marquee> (2020) by xnx on Sunday June 08, 2025 @11:50AM (#44217697)
SPAs were a low point, but I've found consistent and linkable URLs has gotten better with developers recognizing the importance due to "SEO".
Re:<Blink> and <Marquee> (2020) by catlifeonmars on Sunday June 08, 2025 @12:10PM (#44217827)
[delayed]
Re:<Blink> and <Marquee> (2020) by no_wizard on Sunday June 08, 2025 @01:27PM (#44218291)
There se excretes to this, particularly if you value speedy vs delayed updates to your indexing