MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: WebView2 Fixed Runtime does not support PlayReady functionality.

Open
#4,632 2 comments 0 reactions 1 assignee View on GitHub

@champnic is already working on this.

Since Jun 18, 2024.

bug
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

What happened?

We're encountering an issue where the WebView2 Fixed Runtime does not support PlayReady functionality. Applications such as ours (Cider) that rely on PlayReady DRM for media playback experience compatibility problems when using the WebView2 Fixed Runtime. This lack of support results in failures to play protected content as expected.

Currently, this limitation is impacting our ability to provide secure media playback within our application. We need PlayReady support in the WebView2 Fixed Runtime to ensure compatibility with our DRM requirements and maintain a consistent user experience.

Importance

Blocking. My app's basic functions are not working due to this issue.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

123.0.2420.81

SDK Version

1.0.1264.42

Framework

WPF

Operating System

Windows 11

OS Version

26100.560

Repro steps
  1. Set up the Environment

    • Create a simple basic WPF WebView2 project.
    • Setup the latest version of the WebView2 Fixed Runtime instead of using Evergreen/System's installation.
  2. Prepare project

    • Implement or test content protected by PlayReady DRM in the application.
  3. Launch the Application

    • Start the application and navigate to a page or content that requires PlayReady DRM for playback.
  4. Observe the Issue

    • Attempt to play the DRM-protected content.
    • Application does not properly playback the encrypted stream/video/audio.
Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

Don't know

Last working version (if regression)

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.