User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:126.96.36.199) Gecko/20101203 Firefox/3.6.13 (.NET CLR 3.5.30729) Build Identifier: I would like to see attributes be added to allow iframes to have independent navigation controls. Especially but not exclusively for larger screens, one can envision, for example, a site which displays content in a table, with paragraphs being in one column, and commentary in another. If the commentary column uses say a wiki (or a comment feed/discussion thread), to keep track of resources and cross-references, insights, errata, etc. pertaining to a given paragraph or verse (e.g., for books, but also potentially for blog articles, etc.--anywhere people may wish to dissect in context), it would be desirable for one to be able to say edit content in one fixed iframe pane, follow links in another one (including to other domains), etc., all while keeping the original context of the table of content and iframes on screen, and allowing the user to go backward and forward in any pane independently (or possibly type in a URL bar for each iframe). One can even imagine ongoing chat discussions taking place within such a mosaic. I brought this up on the HTML5 list, and got a response from Ian Hickson, which, though favorable, pointed me to the need for implementation experience: http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-August/027884.html So, this is not something which is apparently ripe for standardization yet, but I was hoping you might have interest to provide some non-standard attributes to experiment. I would hope at least for the option to turn on small back and forward buttons, and possibly as another attribute/value, the ability to have a small independent URL bar, though this is not as essential to the idea. Reproducible: Always
Is https://wiki.mozilla.org/WebAPI/BrowserAPI and bug 738172 covering the full range of objectives here or am I missing something?
Could not the frameElement property be used to tie together the specific instance of a frame with the element responsible for encapsulating it (and thus add navigation controls to that element): https://developer.mozilla.org/en-US/docs/Web/API/Window/frameElement . Could cross-domain restrictions somehow be lifted in the responsible code to allow the child frame to communicate page history and such back to the encapsulating iframe so it could track navigation controls?