Unfortunately, you then had to figure out what to do if someone accessed the frame page directly, since search engines could still index these parts of the page seperately. And they always felt jarring and awkward too, since the cutoff between sections was always obvious...
In fact, I used them too around 2001 or so for my website when I did not enough programming/scripting to add a common layout to all content pages. That's how I originally implemented a two column layout: a narrow frame on the left for navigation links and a wide one on the right for content. I don't do it anymore, of course. I do know how to program now and generate my HTML website using a tiny Common Lisp program that adds common headers and footers to all my web pages.
Seriously though, why can HTML not have a client side include?
Fix that and give us HTML tables with basic features built-in and datasource-backed tables + list views back in the mid ‘00s and mind-boggling amounts of time and money could have been saved.
Instead, none of that happened, and it still hasn’t.
Don’t even get me started on how much money could have been saved if the Web had adopted payment standards so that the browser itself could handle payment input.
and not exactly the same across different browsers.
Yes kids, there was a time when not everybody was using the same browser.
Here's hoping for another one, just to keep them on their toes.
Unfortunately, it is still used for html formatted emails
Add this how more complex emails could potentially lead to security issues for their webmail clients and waht not...
And well, "eh, good enough" is probably the order of the day.
window.top.callbacks[number]("serializedData™)
In the latter 90s. Would also client render navigation frames at the time. Wicked fast compared to most web apps at the time.