Skip to content

Bug: Is react player not reactive with respect to tracking props? #1193

@tommhuth

Description

@tommhuth

Is there an existing issue for this?

  • I have searched the existing issues

Which Mux Elements/Packages does this apply to? Select all that apply

mux-player-react

Which browsers are you using?

Chrome

Which operating systems are you using?

macOS

Description

We respect the players cookie choice, and have tracking disabled by default and only enable it when cookie information has been accepted. when i do this i get seemingly no tracking at all, even when disableTracking and disableCookies are set to false after page load. is this a non reactive prop that must be initialised to true to get any tracking?

when i default to undefined before setting true, i do get tracking, but is that really the same as always having true if tracking is enabled by default?

Reduced test case

No response

Steps to reproduce

  1. initialze with disableTracking and disableCookies false
  2. update to true
  3. no tracking in network tab even after enabled

Current Behavior

no tracking if inited to false

Expected Behavior

should start tracking after prop is true

Errors

No response

What version of the package are you using?

0.24.0

Metadata

Metadata

Labels

Status: UnconfirmedA potential issue that we haven't yet confirmed as a bug

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions