Refactor "requestnavigation" event triggering / handling
Add cache to httpProxy. Currently this is only used for the landing page.
DOMSprockets polyfilled Element.prototype.hidden (mainly for IE)
and also implemented element `visibilitychange` events.
This requires browser support for `DOMAttrModified` events.
Maintain frameset and frames in a tree.
Recurse this tree to detect frames to be updated in framer.load(),
instead of calling $$('hf:frame')
When a hf:frame enters the document, wait until it becomes visible before
activating it - adding it to the frameset tree, loading its contents.
Refactoring.
- HFrameDefinition wasn't removing hf:body when creating new HFBodyDefinition
- HBodyDefinition didn't need a fragment for non hf:transform children
Refactoring. getNavigationDetails() was only used in framer.onClick()
Add support for @link.
Inline scripts were executing immediately but they should execute synchronously
- Namespaces for custom-elements, via <html custom-hf="HyperFrameset">
- DOMSprockets change - getAttribute('class') instead of className
Bring in some refactoring from DOMSprockets
Implement no @src hf-frame which merely clones the `loaded` hf-body
to render. This allows a container frame outside of a recursive frame tree.