feat(hub-ui): support seamless iframe presentation - #300
Closed
dvcolomban wants to merge 2 commits into
Closed
Conversation
|
@dvcolomban is attempting to deploy a commit to the NuxtLabs Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
presentation?: 'default' | 'seamless'to iframe dock entriescreateUi({ viewer: { background: 'transparent' } })to publish a transparent standalone viewer surface before first paintWhy
Some Hub consumers embed a complete dashboard or another Hub viewer inside an existing devtools surface. The iframe element itself can be borderless while the surrounding address bar, loading background, panel material, or embedded document background still creates a visible rectangular seam.
Presentation belongs to the viewer, but an iframe entry needs a portable way to express that it is intended to share its host's visual surface. The standalone viewer also needs an explicit transparent mode so its document does not repaint that surface from inside the frame.
Visual comparison
Compatibility
Both capabilities are opt-in. Existing iframe entries and
createUi()calls retain their current presentation. Other viewers may supportseamlesswith an equivalent treatment or keep their default rendering.Validation