# Issues with player events in Safari 13.1 webcomponents?

**URL:** <https://community.bitmovin.com/t/issues-with-player-events-in-safari-13-1-webcomponents/760>\
**Category:** Support\
**Tags:** bitmovin-player, safari\
**Created:** [May 22, 2022, 9:07pm UTC](https://community.bitmovin.com/t/issues-with-player-events-in-safari-13-1-webcomponents/760 "2022-05-22T21:07:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![matheus.cardoso](https://avatars.discourse-cdn.com/v4/letter/m/3bc359/32.png) [@matheus.cardoso](https://community.bitmovin.com/u/matheus.cardoso)\
**Post date:** [May 22, 2022, 9:07pm UTC](https://community.bitmovin.com/t/issues-with-player-events-in-safari-13-1-webcomponents/760/1 "2022-05-22T21:07:19Z")

</div>

Do you know if there are any issues with player events in Safari 13.1 browsers when embedding the player in a webcomponent?

---

<div class="post-metadata">

**Author:** ![anon23459950](https://avatars.discourse-cdn.com/v4/letter/a/977dab/32.png) [@anon23459950](https://community.bitmovin.com/u/anon23459950)\
**Post date:** [May 22, 2022, 9:10pm UTC](https://community.bitmovin.com/t/issues-with-player-events-in-safari-13-1-webcomponents/760/2 "2022-05-22T21:10:11Z")

</div>

Yes, due to a bug in Safari 13.1 some player events are not properly (re-)triggered if the player is inside a webcomponent. The Bitmovin engineering teams are aware of this and are looking into this to see if they find a workaround for this bug in Safari. If this is affecting your implementation please keep an eye on the release notes of future updates.