The FrameControl provides an alternative programming model for developing UI in Ibiza. This alternative gives the extension author full control over the DOM via an IFrame.
While this programming model results in maximum flexibility, FrameControls are not Ibiza Fx controls so extension developers are responsible for
- Accessibility - Making the blade accessible, as specified in portalfx-accessibility.md
- Theming - The extension's UI should always reflect the user's currently selected theme, and should react dynamically when the user changes themes
- Consistent Look & feel - Designing a visual experience that is consistent with the rest of Ibiza
Use FrameControl under the following conditions.
- An existing web experience needs to be migrated to Ibiza without being re-implemented
- An existing web experience needs to be hosted in many environments where Ibiza is just one of the hosts
- Developers want to implement user interactions and experiences that are not supported by Ibiza Framework components. For example, you need to build a very rich, custom UX that is not likely to be reused across services.
- When using AppBlade, developers are responsible for the following.
- Try to use a built-in control when possible, even if it means a little more work up front.
- Don't underestimate the cost of accessibility and alignment with portal look and feel
Go to the playground site to use the latest control and get source code for your project. Learn more about playground.