Skip to content

Initialise before setting protection data in MSE Strategy #390

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 13 commits into from
Jun 3, 2025

Conversation

jlks
Copy link
Contributor

@jlks jlks commented Jun 2, 2025

📺 What

Initialise before setting protection data (as in dash.js examples). Add extra info logging.

🛠 How

  • Move initialize call
  • Info log [Protection prefixed messages to cover calls through to ProtectionController/ProtectionModel.

@jlks jlks self-assigned this Jun 2, 2025
@jlks jlks requested a review from a team as a code owner June 2, 2025 15:15
@jlks jlks added the semver patch This PR is a semver patch release label Jun 2, 2025
ShiningTrapez
ShiningTrapez previously approved these changes Jun 3, 2025
Copy link
Contributor

@eirikbjornr eirikbjornr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small change I'd really like

@@ -506,7 +507,9 @@ function MSEStrategy(
}

function onDebugLog(event) {
DebugTool.debug(event.message)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we retain this with an if-else? So we've got Dash.js logs on DebugTool.debug

@jlks jlks merged commit c244682 into master Jun 3, 2025
4 checks passed
@jlks jlks deleted the post-initialize-prot-data branch June 3, 2025 12:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver patch This PR is a semver patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants