forked from shaka-project/shaka-player
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
In many places, the implicit type info was insufficient. For example, document.createElement returns Element, but the actual return is always a subclass of Element. In many cases, we need the compiler to know that a specific subclass is in use, so that it can correctly check our use of subclass-specific properties. Another common pattern is confusion between Node and Element (which is a subclass of Node). Almost all of the changes in the demo and UI are Element-related. In some places, we referred to HTMLMediaElement, used in the Player API, instead of the more specific HTMLVideoElement in use in our demo. Since the demo uses video-specific properties, we must use the more specific type. Another case is the use of document.createEvent, which returns Event according to the compiler, but in reality always returns a subclass, like CustomEvent. In one case in NetworkingEngine, correcting the type of an AbortableOperation led to the discovery that we had been incorrectly accessing a private method of that type. In goog.Uri, there were several instances of "*" for a type, which the newer compiler won't accept. These have all been corrected. Finally, in some places, we had the wrong nullability on a type. These were all caught by a compiler upgrade. Issue shaka-project#2528 Change-Id: I7f2d070e3da32fe9ff5f444315649f3cbdb5a4a5
- Loading branch information
1 parent
34cde38
commit 07335d7
Showing
12 changed files
with
97 additions
and
65 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.