Traditional HTML frames, introduced with HTML 4.0, were useful for their ability to combine several distinct web pages into a single view. However, several problems arose from the implementation and as such, frames were removed from the W3C
XHTML 1.1 standard. XFrames was supposed to address some of the following problems existent in HTML frames: • a web browser's “back” button failing to work intuitively • the failure to bookmark or favorite specific documents on the web page easily as well as the inability to send an individual a reference to a specific document or collection • getting trapped in a frameset • the production of different results at times when a web page containing frames is reloaded • the "Page Up" and "Page Down" keys being difficult to use due to the pointer focus being on another frame within the page • security vulnerabilities caused by the fact that a user has no way of knowing the original source of each framed document • Since frames are not supported by all agents, and the necessary content is not popularly implemented, agents that do not support frames (such as search engines) fail to render pages correctly and at the same time prevent any
search engine optimization. XFrames overcomes the bookmarking problem by encoding the population of the frames into the URI, thus making it possible to bookmark/add a favorite of a page successfully. ==XFrames implementation==