Skip to content

fix: check for legacy Fairplay support when switching out of handleEncryptedEvent#234

Merged
Essk merged 1 commit intomainfrom
fix/check-for-legacy-fairplay-support-when-switching-out-of-handleEncryptedEvent
Jul 15, 2025
Merged

fix: check for legacy Fairplay support when switching out of handleEncryptedEvent#234
Essk merged 1 commit intomainfrom
fix/check-for-legacy-fairplay-support-when-switching-out-of-handleEncryptedEvent

Conversation

@Essk
Copy link
Contributor

@Essk Essk commented Jul 7, 2025

If we attempt to play content with both legacy Fairplay and Widevine DRM configured in Chrome, something like this:

{
    "com.apple.fps.1_0": {
    ......
    },

    "com.widevine.alpha": {
        "url": "xxxxxxx.xxxxx.xxxx",
    }
},

is passed to handleEncryptedEvent, where this check detects the presence of the legacy Fairplay configuration, exits out and, as we're in Chrome, playback can't start as Fairplay isn't supported.

This change adds a simple additional check for WebKitMediaKeys for confirmation that the platform supports legacy Fairplay before exiting out of handleEncryptedEvent.

@Essk Essk requested a review from adrums86 July 7, 2025 14:55
Copy link

@adrums86 adrums86 left a comment

Choose a reason for hiding this comment

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

:shipit:

@Essk Essk merged commit 595f2ad into main Jul 15, 2025
4 checks passed
@Essk Essk deleted the fix/check-for-legacy-fairplay-support-when-switching-out-of-handleEncryptedEvent branch July 15, 2025 15:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants