Skip to content
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

Updating my repo #2

Merged
merged 5 commits into from
May 6, 2021
Merged

Conversation

surajkumar-sk
Copy link
Owner

Description

Screenshots (optional)

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to
    not work as expected)
  • This change requires a documentation update

Checklist:

  • I have signed the Google CLA https://cla.developers.google.com
  • My code follows the style guidelines of this project
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • I have verified my change on multiple browsers on different platforms
  • I have run ./build/all.py and the build passes
  • I have run ./build/test.py and all tests pass

joeyparrish and others added 5 commits May 4, 2021 15:37
Previously, we faked a single "video/mp4" variant for all src=
playbacks.  This resulted in a failure when someone tried to use src=
with encrypted WebM and ClearKey.  The correct MIME type and codec
needs to be sent to DrmEngine so that it can send the correct metadata
to EME.

Closes #3366

Change-Id: If4f12e0a800d07e84caaae0f6322f549a90b2a95
The "License Header" in custom content was an h3 element, and it was
huge.  This makes it a div with a more reasonable style.

It seems better to me to use div instead of h3, since h3 implies a
third-level of a hierarchy that does not exist here.

Change-Id: I1f8c115a768924f827c5c87dc59bf4146e5e54d1
When switching from using document.createEvent to using the CustomEvent
constructor, we accidentally broke the "shaka-ui-load-failed" event
such that it no longer had a detail object. The detail object is meant
to be provided, not by itself, but as a member variable inside a custom
dictionary.
This fixes the syntax on the constructor.

Issue #3388

Change-Id: I16dc025c21c8f0a012b5854bbbc56e8b110b2300
@surajkumar-sk surajkumar-sk merged commit 68499bf into surajkumar-sk:master May 6, 2021
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.

3 participants