browser vendors such as Apple with Cyberdog followed later that year. At that time, Netscape proposed frames to the World Wide Web Consortium (W3C) for inclusion in the HTML 3.0 standard. Frames were used to display and navigate early online magazines and web apps, such as webmail services and web chat sites. Frames had the advantage of allowing elements to be displayed sitewide without requiring server features such as server-side includes or CGI support. These features were not common on early web servers accessible to the public. Early websites often used a frame at the top to display a banner which could not be scrolled away. These banner frames sometimes included the site's logo as well as advertising. XHTML 1.1, the intended successor to HTML 4, removed all frames. XFrames, the intended eventual replacement, provided the composite URI to address a populated frameset. The later HTML5 standard removed framesets by means differing from XHTML. The iframe element remains with a number of "sandboxing" options intended for sharing content between sites. Advantages By allowing content to be loaded and navigated independently, frames offered several advantages over the plain HTML in use when they were first developed: Simplifying maintenance of content shared across all or most pages, such as navigation data. If an item needs to be added to a sidebar navigation menu, the web page author needs to change only one web page file, whereas each individual page on a traditional non-frameset website would have to be edited if the sidebar menu appeared on all of them. Reducing the amount of bandwidth needed by not re-downloading parts of the page which had not changed. Allowing several pieces of information to be viewed side by side, with the ability for each section to be scrolled independently. This might include the side-by-side comparison of two pictures or videos, or two different ways to understand something, such as an independently scrolling page of text next to video, images, animation, 3D rotating objects, etc. Allowing footnotes or digressions to appear in a dedicated section of the page when linked to, so that the reader does not lose their place in the main text. Criticism The practice of framing HTML content led to numerous criticisms, most centering on usability and accessibility concerns. These include: Framing breaks the identity between the content and URL as displayed in the browser, making it difficult to link to or bookmark