Framing (World Wide Web)
From Seo Wiki - Search Engine Optimization and Programming Languages
This article needs additional citations for verification. Please help improve this article by adding reliable references. Unsourced material may be challenged and removed. (January 2008) </td> </tr> </table>
For other uses, see Framing (disambiguation).
On a web page, framing means that a website can be organized into frames. Each frame displays a different HTML document. Headers and sidebar menus do not move when the content frame is scrolled up and down. For developers frames can also be convenient. For example, if an item needs to be added to the sidebar menu, only one file needs to be changed, whereas each individual page on a non-frameset website would have to be edited if the sidebar menu appeared on all of them. However, server-side includes and scripting languages such as PHP can also be used to accomplish this aim without some of the drawbacks of frames such as confusing the operation of the address bar and back and forward buttons.
History
Netscape 2.0 introduced the elements used for frames in the 1990s (see Netscape Navigator). At that time, Netscape proposed frames to the W3C for inclusion in the HTML 3.0 standard.[1] SyntaxThe frameset replaces the <frameset cols="85%, 15%"> <frame src="URL OF FRAME PAGE 1 HERE"> <frame src="URL OF FRAME PAGE 2 HERE"> <noframes> Text to be displayed in browsers that do not support frames </noframes> </frameset> Content sourcesSee also: Mirror (computing)
The contents of the frames may be hosted on the same server as the parent page, or it may link in code from another website server such that these external contents are automatically displayed within the frame (transclusion or remote loading). This may be confusing and inconvenient to the users: they can get the impression that the information belongs to the same website; also, less than the full browser window is available and the address bar is less informative. Some websites request not to be used in this way on other websites; some discourage it by including a framekiller script in its pages. The framing website runs a risk of being blamed for external content that, for example, is or becomes inaccurate or objectionable.[3] In addition, there may be legal issues associated with framing, in that the owner of the external content may object to the involuntary (and possibly objectionable) implied association with the framing website. Visitors may confuse ownership of copyrights or trademarks of the external site with the owner of the framing site. CriticismChief criticism of the practice of framing HTML content includes:
ReplacementsAlthough frames were included in the XHTML 1.0 specification, they were not carried across to XHTML 1.1. The intended eventual replacement is XFrames,[8] which attempts to solve the problem of addressing a populated frameset through composite URIs. For those serving web content under the XHTML 1.0 specification, documents may be embedded within one another via either the Frames become invalid in HTML5[9], with the exception that iframes remain.[10] See alsoReferences
External links
de:Frame (HTML) it:Frameset nl:Frame (HTML) pt:Enquadramento (World Wide Web) ru:Фрейм (HTML) |
↓