4 ms·
"Campaign against Frames" A quick google search lead to this https://tintara.tripod.com/FramesSuck.html https://tintara.tripod.com/FramesSuck.html It is interes
by KyleBerezin 4y ago
"Campaign against Frames" A quick google search lead to this https://tintara.tripod.com/FramesSuck.html https://tintara.tripod.com/FramesSuck.html It is interesting to see what are now basic html features used to be contested.
- chrisco255 4y agoFrames have been deprecated: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/frame https://developer.mozilla.org/en-US/docs/Web/HTML/Element/fr... They were very commonly used in 90s websites. Typically, you would create one html page for a Nav bar on the left and multiple html pages for your content that would appear in a content frame. In creating a link on the nav, you'd have to specify to render the content in the appropriate frame. They fell out of favor in the early-mid 00s due to issues with proper rendering on various screensizes and browsers. In addition, web crawlers could not know whether a page was supposed to be rendered within a navigation context or not, so you'd often find google linking to content pages but without the navigation frame included, leaving users stranded on the page. iframes solved these issues to a large extent, along with better, more powerful CSS.
- npteljes 4y agoFrames were (and to an extend still are) heavily abused for advertising and other purposes. You could, for example, hide the real URL of a page. The user would go to the page, the page would contain the frameset, and the frames would just load content from wherever. Really broke the promise of the URL bar, which would suggest that the page you're seeing belongs to the URL displayed.