Skip to content

fix: correctly detect Edge Chromium as Edge#2855

Merged
joeyparrish merged 1 commit intoshaka-project:masterfrom
valotvince:patch-2
Sep 17, 2020
Merged

fix: correctly detect Edge Chromium as Edge#2855
joeyparrish merged 1 commit intoshaka-project:masterfrom
valotvince:patch-2

Conversation

@valotvince
Copy link
Contributor

@valotvince valotvince commented Sep 17, 2020

Edge Chromium UA example: User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.74 Safari/537.36 Edg/79.0.309.43

Since #2801, trying to play PlayReady content with Shaka on Edge Chromium would result in a MANIFEST_RESTRICTIONS_CANNOT_BE_MET error since it wasn't selected to do the endianness black magic.

Edge Chromium should be detected as Edge to correctly correct the key endianness.

This affects the v3.0.4 and v2.5.16 releases.

@joeyparrish joeyparrish merged commit a344f10 into shaka-project:master Sep 17, 2020
matEhickey pushed a commit to matEhickey/shaka-player that referenced this pull request Sep 25, 2020
Without this, shaka-project#2801 is broken on the latest versions of Edge
matEhickey pushed a commit to matEhickey/shaka-player that referenced this pull request Sep 25, 2020
Without this, shaka-project#2801 is broken on the latest versions of Edge
joeyparrish pushed a commit that referenced this pull request Sep 29, 2020
Without this, #2801 is broken on the latest versions of Edge
@valotvince valotvince deleted the patch-2 branch September 30, 2020 15:02
@valotvince
Copy link
Contributor Author

valotvince commented Sep 30, 2020

@joeyparrish I would suggest to have a line in the changelog on the impacted Releases to warn potential users about that issue

@joeyparrish
Copy link
Member

We haven't made a new release yet, but I'm working on it. The fix will be in v3.0.5 and v2.5.17 and will definitely be mentioned in the changelog and release announcement.

joeyparrish pushed a commit that referenced this pull request Oct 1, 2020
Without this, #2801 is broken on the latest versions of Edge
@github-actions github-actions bot added the status: archived Archived and locked; will not be updated label Jul 25, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

status: archived Archived and locked; will not be updated

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants