fix: use uiContainer to apply position when creating shadow root ui #1939
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.
Overview
This is a companion PR for aklinker1/webext-core#118
Once the shadow DOM uses a
<div>instead of constructing a full HTML document, the current approach of finding the<html>element won't work. Instead, theuiContainerwill be used to position the content script UI.Manual Testing
How to test this change:
pnpm dlx wxt@latest initwxtwxtrepopnpm buildinwxt/packages/wxtpnpm link <path-to-wxt/packages/wxt>to use modified version ofwxtwebext-corewebext-corerepobun run buildinwebext-core/packages/isolated-elementwxtdirectory, runpnpm link <path-to-webext-core/packages/isolated-element>to use modified version of@webext-core/isolated-elementcreateShadowRootUiwith positionoverlayormodalto verify that the element is position as desiredExample code for testing: