TODO

• HyperFrameset could run in a full-sized overlaying <iframe>.

  • This would allow the document for the current URL to populate the top window (just like normal browsing).
  • It could make switching between "basic" and "frameset" modes simpler
  • Might allow some sort of virtualization of the "frameset" DOM
  • Might mean line numbers in scripting errors in frameset actually line up.

• Alternatively could use redirection to the frameset page (only if frameset page is in the scope dir of landing page)

  • This would allow HyperFrameset to work on file:/// under Firefox - see cross-site restrictions
  • Could use interception
  • This is actually more effective than "capturing" at defeating the browser preloader.
  • Might mean line numbers in scripting errors in frameset actually line up.

• Transformers, decoders, filters should be independent of HyperFrameset (see "interception")

  • Ideally "interception" would be a dependency of HyperFrameset.

• easier to switch off HyperFrameset (go into "basic" mode). Perhaps something like Turbolinks

• bookmarklet for configuring user options

• httpProxy cache-control (see ServiceWorker)

• predictnavigation or similar events

• httpProxy caching for predictnavigation

• setActiveStylesheet(). See http://alistapart.com/article/alternate

• same-page links aren't handled

• forwards / back doesn't seem robust

• bfcache + scroll restore

• prefetching from config.js or speculative fetching from examining frameset markup

• submit handling for POST, PUT, etc

• modal and non-modal dialogs

• declarative format for converting navigation requests to target frame(s) name. This will replace / augment lookup() definitions.

• processing variables passed to frame transforms

• more complex changesets for navigation requests. e.g. multiple targets and even multiple URLs

• <hf-frame> disabling while hidden is shoddy

• frame transition animations

• frame transition callbacks

• more error handling

• binding (DOMSprockets?) sets for <hf-frame>

• enteredState / leftState need more info, especially oldURL / newURL

• per-frame state signals

• more powerful layout and dimensioning for panels (see ampproject maybe)

• use IntersectionObserver

• floating panels - panels that can be responsively pinned / floating / popup

• more boot-url params. e.g. configdir, scriptdir

• scoped boot options OR something like a site-map

• support XHTML templates

• Linting tools for frameset documents

• frameset visual designer

• Allow config.js to be inlined with options.js and boot.js