The client-side implementation of the frames model.
A web application can consist of a series of pages embedded within the body of another page, i.e. it is possible to nest XDIME 2 documents (i.e. html elements and their descendants) inside the body of another XDIME 2 document. In frame mode, each html element that is the first-level descendant of the root html element defines a frame page. A dynamic container for a frame page is called frame. Its position with the layout is specified by the frame region. The frame page contained within a frame can be replaced by another frame page as the user navigates through the application. The navigation history is maintained across all frames in the application.
The frame pages must all be part of a single XDIME 2 page, i.e. after DCI processing has been performed the resulting output must contain all the pages that are used within that page.
The set of frame pages within the actual page is fixed, e.g. if the actual page uses client-side frames it is not possible to wrap a page in ui:prototype and use that to create additional pages.
n/a
The following table lists the components that provide support for different elements of the frames model.
| Component | Purpose |
|---|---|
| Frame component | This component provides the client-side representation of a frame. |
| Frame page component | This component provides the client-side representation of a frame page. |
| History component | This component provides a means for a frame to keep track of the history of pages displayed in that frame. |
See also: Using the frame components.