Move fenced frame config instance to browsing context #90
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.
This is a partial follow-up to the discussion in #84 (comment). All this does is move the fenced frame config instance from navigable => browsing context, and updates the advisement text around it and all usages.
A follow-up to this will finalize the config instance assignment to happen at the time where a new browsing context group is chosen for the fenced frame for embedder-initiated navigations, so that the config instance is always wiped.
Preview | Diff