Troubleshooting

“<bw-player-provider> parent not found”

An element that extends BwPlayerConsumer was used outside a <bw-player-provider>. Make sure the provider wraps every control.

The elements expect the player to be available as the global BeyondWords. Load the player UMD script before the provider connects:

<script async src="https://proxy.beyondwords.io/npm/@beyondwords/player@latest/dist/umd.js"></script>

The engine renders its own UI by default. Set data-show-user-interface="false" on the provider so only your UI shows:

<bw-player-provider data-project-id="9504" data-source-id="…" data-show-user-interface="false"></bw-player-provider>

A custom element only upgrades once its module has run customElements.define. Make sure you’ve imported each element’s module:

<script type="module">
  import "@/registry/html/PlayerProvider";
  import "@/registry/html/PlayPauseButton";
</script>

The elements are minimal by design. They render into the light DOM, so your page’s CSS can target them directly. See Theming.

Check the data-project-id and data-source-id (or content ID) are valid for your project.
Browsers block audio until the user interacts with the page, so the first playback must come from a user action like a click.