createShadowRootUi styles not taking effect in shadow DOM (wxt + naive-ui)

[shijunpeng15]

Describe the bug

I'm using the wxt framework and naive-ui's createShadowRootUi method to create a shadow DOM interface, but the styles aren't taking effect.
naive-ui inline styles not applying in Shadow DOM via createShadowRootUi (wxt)

// App.vue
<template>
  <NConfigProvider>
    <NMessageProvider>
      <NDialogProvider>
        <NNotificationProvider>
          <NButton type="info"> Info </NButton>
        </NNotificationProvider>
      </NDialogProvider>
    </NMessageProvider>
  </NConfigProvider>
</template>
<script lang="ts" setup>
import {
  NButton,
  NConfigProvider,
  NDialogProvider,
  NMessageProvider,
  NNotificationProvider,
} from 'naive-ui';
</script>

<style scoped></style>

// content.ts
import { createApp } from 'vue';
import { createShadowRootUi } from 'wxt/client';
import { defineContentScript } from 'wxt/sandbox';
import App from '../contentui/goods/App.vue';
import '../contentui/goods/content.css';  // content.css is empty

export default defineContentScript({
  matches: ['<all_urls>'],
  cssInjectionMode: 'ui',
  async main(ctx) {
    const ui = await createShadowRootUi(ctx, {
      name: 'naive-ui-container',
      position: 'inline',
      anchor: 'body',
      onMount: (container) => {
        const app = createApp(App);
        app.mount(container);
        return app;
      },
      onRemove: (app) => {
        app?.unmount();
      },
    });
    ui.mount();
  },
});

Reproduction

..

Steps to reproduce

No response

System Info

System:
    OS: Windows 11 10.0.26100
    CPU: (20) x64 13th Gen Intel(R) Core(TM) i5-13600K
    Memory: 16.99 GB / 31.75 GB
  Binaries:
    Node: 23.10.0 - ~\AppData\Roaming\fnm\aliases\default\node.EXE
    npm: 10.9.2 - ~\AppData\Roaming\fnm\aliases\default\npm.CMD
    pnpm: 10.6.5 - ~\AppData\Roaming\fnm\aliases\default\pnpm.CMD
  Browsers:
    Edge: Chromium (128.0.2739.67)
    Internet Explorer: 11.0.26100.1882

Used Package Manager

pnpm

Validations

• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[aklinker1]

https://wxt.dev/guide/resources/faq.html#my-component-library-doesn-t-work-in-content-scripts