shaka-player 4.4.3 → 4.6.0

package/docs/design/lcevc-integration.md

@@ -8,51 +8,51 @@ This article describes the V-Nova LCEVC Shaka Player integration.
 # LCEVC Integration
 
 ## Adding V-Nova required files
-### Importing DIL - Decoder Integration Layer
+### Importing LCEVC Decoder
 
-V-Nova LCEVC DIL Libraries are included using the same approach that the other external libraries are currently using. The necessary V-Nova LCEVC DIL files need to be imported in the HTML page that is going to be used by Shaka Player to decode LCEVC. Checks are inplace that make sure the necessary objects are available.
+V-Nova LCEVC Decoder Libraries are included using the same approach that the other external libraries are currently using. The necessary V-Nova LCEVC Decoder files need to be imported in the HTML page that is going to be used by Shaka Player to decode LCEVC. Checks are inplace that make sure the necessary objects are available.
 
-Npm package : <https://www.npmjs.com/package/lcevc_dil.js>
+NPM package : <https://www.npmjs.com/package/lcevc_dec.js>
 
 ```javascript
   <!-- MPEG-5 Part2 LCEVC support is enabled by including this: -->
-  <script defer src="../node_modules/lcevc_dil.js/dist/lcevc_dil.min.js"></script>
+  <script defer src="../node_modules/lcevc_dec.js/dist/lcevc_dec.min.js"></script>
 ```
 
-To allow the Closure compiler to use the objects and methods that are exported by the DIL.js a new `extern` is created.
+To allow the Closure compiler to use the objects and methods that are exported by the LCEVCdec.js a new `extern` is created.
 
 ### Defining an Extern for LCEVC
 
-`externs/lcevc.js` exposes the functions from the LCEVC DIL library required for LCEVC Decoding.
+`externs/lcevc.js` exposes the functions from the LCEVC Decoder library required for LCEVC Decoding.
 
 ## Integration point
 
-### The shaka.lcevc.Dil class - (DIL : Decoder Integration Layer)
+### The shaka.lcevc.Dec class - (DEC : Decoder)
 
-The main logic of the LCEVC integration is located in the `lib/lcevc_dil.min.js` file. In this file the shaka.lcevc.Dil is exported to be used in the project. This class is in charge of creating the Dil object using the mentioned externs, checking if LCEVC DIL library is available, etc.
+The main logic of the LCEVC integration is located in the `lib/lcevc_dec.min.js` file. In this file the shaka.lcevc.Dec is exported to be used in the project. This class is in charge of creating the Dec object using the mentioned externs, checking if LCEVC Decoder library is available, etc.
 
 ### Modifications in the player
 
 The shaka.Player class, defined in the `lib/player.js` file, is the main player object for Shaka Player. There is a setter function for setting up a `canvas` element that is received from the user.
 If shaka.ui is used the `canvas` is created in line with the video element in the same container overlaying the video element. If user provides a custom canvas using the setter function, The user is responsible for placing the canvas element in the desired position and resizing it.
 
-`shaka.externs.LcevcConfiguration` is added to the `playerConfiguration` that is used as configuration for the LCEVC DIL Library.
+`shaka.externs.LcevcConfiguration` is added to the `playerConfiguration` that is used as configuration for the LCEVC Decoder Library.
 
-The Dil object is created in the `onLoad_()` event that is triggered when a new video is loaded in Shaka Player. Attaching to a media element is defined as:
+The Dec object is created in the `onLoad_()` event that is triggered when a new video is loaded in Shaka Player. Attaching to a media element is defined as:
 
 -   Registering error listeners to the media element.
 -   Catching the video element for use outside of the load graph.
 
-The Dil object is created only if LCEVC is supported (LCEVC libs are loaded on the page) and also when it was not already created in another `onLoad_()` event execution.
+The LCEVC Decoder object is created only if LCEVC is supported (LCEVC libs are loaded on the page) and also when it was not already created in another `onLoad_()` event execution.
 
 
-### Feeding the Dil
+### Feeding the Dec
 
 The logic that Shaka Player uses to communicate with the Media Source Extensions (MSE) is located in the `media/media_source_engine.js` file.
 
 ![image.png](lcevc-architecture.png)
 
- `append_()` function that is used to feed the MSE Source Buffer is intercepted and modified to pass the video buffers to the LCEVC DIL Libraries before appending to the MSE Source Buffers. 
+ `append_()` function that is used to feed the MSE Source Buffer is intercepted and modified to pass the video buffers and related time offsets to the LCEVC Decoder Libraries before appending to the MSE Source Buffers. 
 
 ## Demo page
 
@@ -60,7 +60,7 @@ The relevant libraries are added in the Demo Page like so:
 
 ```javascript
   <!-- MPEG-5 Part2 LCEVC support is enabled by including this: -->
-  <script defer src="../node_modules/lcevc_dil.js/dist/lcevc_dil.min.js"></script>
+  <script defer src="../node_modules/lcevc_dec.js/dist/lcevc_dec.min.js"></script>
 ```
 
 And a new video sample with enhancement data is added to the `demo/common/assets.js` file under a new source `MPEG-5 Part 2 LCEVC`.

package/docs/tutorials/ad_monetization.md

@@ -7,6 +7,60 @@ other ad providers in v3.1+.
 Please note that the current API is likely to undergo significant
 changes as our support extends.
 
+#### AWS Elemental MediaTailor Integration
+
+Shaka Player provides an integration with the [AWS Elemental MediaTailor][].
+We support Client Side, Server Side and overlays ad insertion.
+
+[AWS Elemental MediaTailor]: https://aws.amazon.com/mediatailor/
+
+All ad insertion experiences are available through the
+{@linksource shaka.extern.IAdManager} object on the Player.
+
+If you're not using Shaka's UI library, you will
+also need to create a `<div>` over your video element to serve as an ad
+container.
+
+Start by initializing the server side logic.
+With Shaka UI:
+
+```js
+const video = document.getElementById('video');
+const ui = video['ui'];
+const controls = video.ui.getControls();
+// If you're using a non-UI build, this is the div you'll need to create
+// for your layout.
+const container = controls.getServerSideAdContainer();
+const player = controls.getPlayer();
+const netEngine = player.getNetworkingEngine();
+const adManager = player.getAdManager();
+adManager.initMediaTailor(container, netEngine, video);
+```
+
+Requesting a Client Side stream:
+
+```js
+const mediaTailorUrl = 'https://d305rncpy6ne2q.cloudfront.net/v1/session/94063eadf7d8c56e9e2edd84fdf897826a70d0df/SFP-MediaTailor-VOD-HLS-DASH/out/v1/b94f3611978f419985a18335bac9d9cb/ddb73bf548a44551a0059c346226445a/eaa5485198bf497284559efb8172425e/index.mpd';
+const mediaTailorAdsParams = {
+  adsParams: {
+    assetid: 'test2',
+    podduration: '15',
+  },
+};
+const uri = await adManager.requestMediaTailorStream(mediaTailorUrl, mediaTailorAdsParams);
+player.load(uri);
+```
+
+Requesting a Server Side stream:
+
+```js
+const mediaTailorUrl = 'https://ad391cc0d55b44c6a86d232548adc225.mediatailor.us-east-1.amazonaws.com/v1/session/d02fedbbc5a68596164208dd24e9b48aa60dadc7/singssai/master.m3u8';
+const uri = await adManager.requestMediaTailorStream(mediaTailorUrl);
+player.load(uri);
+```
+
+Note: overlays ad insertions is the same as server side.
+
 #### IMA SDK Integration
 
 Shaka Player provides an integration with the [Interactive Media Ads][] SDKs.

package/docs/tutorials/basic-usage.md

@@ -52,7 +52,8 @@ function initApp() {
 async function initPlayer() {
   // Create a Player instance.
   const video = document.getElementById('video');
-  const player = new shaka.Player(video);
+  const player = new shaka.Player();
+  await player.attach(video);
 
   // Attach player to the window to make it easy to access in the JS console.
   window.player = player;

package/docs/tutorials/errors.md

@@ -17,7 +17,8 @@ const handleError = (error) => {
   }
 };
 
-const player = new shaka.Player(video);
+const player = new shaka.Player();
+await player.attach(video);
 
 // handle errors that occur after load
 player.addEventListener('error', handleError);

package/docs/tutorials/faq.md

@@ -95,31 +95,6 @@ you see JSON, you will need to [unwrap the response][wrapping].
 
 <hr>
 
-**Q:** Why doesn't getStats() work in Safari?
-
-**A:** To play HLS content on Safari, we default to using Apple's native src=
-playback.  Since the browser handles playback, we don't get much information.
-
-If you want to disable native playback and use MediaSource playback instead,
-configure {@link shaka.extern.StreamingConfiguration|
-`.streaming.useNativeHlsOnSafari`} to false.
-
-<hr>
-
-**Q:** Why doesn't my HLS content work?
-
-**A:** If your HLS content uses MPEG2-TS, you may need to enable transmuxing.
-The only browsers capable of playing TS natively are Edge and Chromecast.  You
-will get a `CONTENT_UNSUPPORTED_BY_BROWSER` error on other browsers due to
-their lack of TS support.
-
-You can enable transmuxing by [including mux.js][] v5.6.3+ in your application.
-If Shaka Player detects that mux.js has been loaded, we will use it to transmux
-TS content into MP4 on-the-fly, so that the content can be played by the
-browser.
-
-<hr>
-
 **Q:** Why does it take so long to switch to HD?
 
 **A:** When Shaka Player's `AbrManager` makes a decision to adapt, we don't
@@ -158,26 +133,18 @@ shaka.net.NetworkingEngine.registerScheme('file', shaka.net.HttpXHRPlugin.parse)
 
 <hr>
 
-**Q:** Why are my CEA-708 captions not showing on Edge or Chromecast?
-
-**A:** Our support for CEA-708 captions requires transmuxing the TS files that
-contain said captions.  Edge and Chromecast, however, have native TS support and
-thus are not required to transmux.
-In order to force those platforms to transmux, set the
-{@link shaka.extern.StreamingConfiguration|`.streaming.forceTransmux`}
-configuration to true.
-
-<hr>
-
 **Q:** Why do I get 404 errors with very large timescales?
 
-**A:** We can't handle content that creates timestamps too large to be
-represented as Numbers in JavaScript (2^53).  Very large timescales require very
-large timestamps (in timescale units), which means we are unable to substitute
-the correct values for `$Time$` in a `<SegmentTemplate>`.  [BigInteger.js][] is
-too large to become a required dependency for Shaka Player.
+**A:** Some content creates timestamps too large to be represented as Numbers
+in JavaScript (2^53).  Very large timescales require very large timestamps (in
+timescale units), which means we are unable to substitute the correct values
+for `$Time$` in a `<SegmentTemplate>`.
+
+We can work around this for platforms that support [`BigInt`][], or in cases
+where we can live with a rounding error (not `$Time$` in `<SegmentTemplate>`).
 
-We recommend reducing your timescale or avoiding `$Time` in `<SegmentTemplate>`.
+If you must use `$Time` in `<SegmentTemplate>` and you must play on devices
+that do not support [`BigInt`][], we recommend reducing your timescale.
 See discussion in [#1667][1667] for details.
 
 <hr>
@@ -202,20 +169,23 @@ you can use the same top-level APIs; but we are dependent on the browser
 handling the streaming.  So we won't support DASH on iOS since the browser
 doesn't support it.
 
-We have another project called [Shaka Player Embedded][] that offers the same
-features and similar APIs for native apps on iOS.  This project uses its own
-media stack, which allows it to play content that would otherwise not be
-supported.  This supports both DASH and HLS manifests.
+In a future version, we plan to support `ManagedMediaSource` on iOS to achieve
+control over both DASH and HLS playback on iOS.  See [#5271][] and the
+[`ManagedMediaSource` W3C spec proposal][]
 
 <hr>
 
 **Q:** The Nightly Demo isn't loading for me!
 
 **A:** Are you looking at the uncompiled build with an AdBlocker enabled?
-We're rolling out ad support which is triggering some ad blockers to block
-requests for some of our source files. This only affects the uncompiled build.
+
+Some ad blockers decide to block requests for some of our source files simply
+because they have `ad` in the file name. This only affects the uncompiled
+build.
+
 Switch to the compiled build (add "build=compiled" to the url) or temporarily
-disable your ad blocker to see the nightly uncompiled mode.
+disable your ad blocker to see the nightly in uncompiled mode.
+
 Please note that if you want to test our ad logic, you might have to disable
 the ad blocker in compiled mode as well.
 
@@ -243,11 +213,11 @@ an HLS manifest, we do our best to guess what the codecs might be, but those
 guesses might not always be accurate.  If an HLS manifest has no codec
 information provided, we default to guessing that the video codec is
 `avc1.42E01E` and the audio codec is `mp4a.40.2`, which can cause problems if
-the stream is actually video-only or audio-only.  In this case, you can enable
-the {@link shaka.extern.ManifestConfiguration|`.manifest.disableVideo`} or 
-{@link shaka.extern.ManifestConfiguration|`.manifest.disableAudio`} 
-configurations to signal that your content does not have a video or audio 
-stream.
+the stream is actually video-only or audio-only.
+
+To change our default assumptions about codecs in HLS, please see
+{@link shaka.extern.HlsManifestConfiguration|`.manifest.hls`} in the player
+config.
 
 <hr>
 
@@ -269,8 +239,10 @@ proxy them.
 [887]: https://github.com/shaka-project/shaka-player/issues/887
 [999]: https://github.com/shaka-project/shaka-player/issues/999
 [1667]: https://github.com/shaka-project/shaka-player/issues/1667
-[BigInteger.js]: https://github.com/peterolson/BigInteger.js
+[#5271]: https://github.com/shaka-project/shaka-player/issues/5271
+[BigInt]: https://caniuse.com/bigint
 [CORS]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS
+[`ManagedMediaSource` W3C spec proposal]: https://github.com/w3c/media-source/issues/320
 [Shaka Player Embedded]: https://github.com/shaka-project/shaka-player-embedded
 [auth]: https://shaka-player-demo.appspot.com/docs/api/tutorial-license-server-auth.html
 [buffering]: https://shaka-player-demo.appspot.com/docs/api/tutorial-network-and-buffering-config.html

package/docs/tutorials/index.json

@@ -24,5 +24,6 @@
   { "selenium-grid-config": { "title": "Selenium Grid Config" } },
   { "faq": { "title": "Frequently Asked Questions" } },
   { "upgrade": { "title": "Upgrade Guide" } },
-  { "upgrade-manifest": { "title": "ManifestParser Upgrade Guide" } }
+  { "upgrade-manifest": { "title": "ManifestParser Upgrade Guide" } },
+  { "lcevc": { "title": "LCEVC Quick Start" } }
 ]

package/docs/tutorials/lcevc.md

@@ -0,0 +1,118 @@
+# LCEVC Quick Start 
+ 
+#### Requirements 
+ 
+ - Only supported on browsers with Media Source Extensions SourceBuffer support 
+ 
+ - MPEG-5 Part2 LCEVC decoding support (decoding provided by [lcevc_dec.js][], 
+ must be separately included) 
+ 
+##### Integration documentation : [docs](../design/lcevc-integration.md) 
+ 
+##### More on [MPEG-5 Part2 LCEVC][] 
+ 
+[lcevc_dec.js]: https://www.npmjs.com/package/lcevc_dec.js?activeTab=readme
+[MPEG-5 Part2 LCEVC]: https://www.lcevc.org 
+ 
+#### Configure LCEVC 
+ 
+LCEVC Decoder library needs to be included in the HTML page: 
+ 
+- Local `npm install lcevc_dec.js` 
+```html 
+<script src="../node_modules/lcevc_dec.js/dist/lcevc_dec.min.js"></script> 
+``` 
+- Or use `unpkg.com` for latest LCEVC Decoder libraries.
+```html 
+<script src="https://unpkg.com/lcevc_dec.js@1.0.0/dist/lcevc_dec.min.js"></script> 
+``` 
+ 
+Configuration to enable LCEVC enhancement: 
+```js 
+player.configure('lcevc.enabled', true); 
+``` 
+ 
+#### LCEVC setup via UI library 
+ 
+Sample setup using the Shaka Player UI library:  
+ 
+```html 
+<!DOCTYPE html> 
+<html> 
+  <head> 
+    <!-- Shaka Player UI compiled library and default CSS for player controls: --> 
+    <script src="dist/shaka-player.ui.js"></script> 
+    <link rel="stylesheet" href="dist/controls.css" /> 
+ 
+    <!-- LCEVC decoder compiled library --> 
+    <script src="https://unpkg.com/lcevc_dec.js@1.0.0/dist/lcevc_dec.min.js"></script> 
+ 
+    <!-- Application source: --> 
+    <script src="app.js"></script> 
+  </head> 
+ 
+  <body> 
+    <!-- The data-shaka-player-container tag will make the UI library place the controls in this div. --> 
+    <div data-shaka-player-container style="max-width:40em"> 
+      <!-- The data-shaka-player tag will make the UI library use this video element. --> 
+      <video data-shaka-player id="video" style="width:100%;height:100%"></video> 
+    </div> 
+  </body> 
+</html> 
+``` 
+ 
+```js 
+// app.js 
+ 
+const manifestUri = 'https://dyctis843rxh5.cloudfront.net/vnIAZIaowG1K7qOt/master.m3u8'; 
+ 
+// Initialise Shaka Player with LCEVC enhancement. 
+async function init() { 
+  // When using the UI, the player is made automatically by the UI object. 
+  const video = document.getElementById('video'); 
+  const ui = video['ui']; 
+  const controls = ui.getControls(); 
+  const player = controls.getPlayer(); 
+ 
+  // Enable the LCEVC enhancement. 
+  player.configure('lcevc.enabled', true); 
+ 
+  // Listen for error events. 
+  player.addEventListener('error', onError); 
+  controls.addEventListener('error', onError); 
+ 
+  // Try to load a manifest. 
+  // This is an asynchronous process. 
+  try { 
+    await player.load(manifestUri); 
+    // This runs if the asynchronous load is successful. 
+    console.log('The video has now been loaded!'); 
+  } catch (error) { 
+    onError(error); 
+  } 
+} 
+ 
+// Handle errors. 
+function onError(error) { 
+  console.error('Error', error); 
+} 
+ 
+// Listen to the custom shaka-ui-loaded event, to wait until the UI is loaded. 
+document.addEventListener('shaka-ui-loaded', init); 
+// Listen to the custom shaka-ui-load-failed event, in case Shaka Player fails 
+// to load (e.g. due to lack of browser support). 
+document.addEventListener('shaka-ui-load-failed', onError); 
+ 
+``` 
+ 
+#### User provided canvas 
+ 
+User can also provide a canvas to the player though `attachCanvas` function: 
+ 
+```js 
+player.attachCanvas(canvas); 
+``` 
+ 
+Note: If external canvas is used, user is responsible for managing 
+the canvas. If no canvas is provided for Shaka UI library, the player 
+will generate and manage the canvas. 

package/docs/tutorials/offline.md

@@ -79,14 +79,14 @@ the end of the tutorial.
 ```js
 // myapp.js
 
-function initApp() {
+async function initApp() {
   // Install built-in polyfills to patch browser incompatibilities.
   shaka.polyfill.installAll();
 
   // Check to see if the browser supports the basic APIs Shaka needs.
   if (shaka.Player.isBrowserSupported()) {
     // Everything looks good!
-    initPlayer();
+    await initPlayer();
   } else {
     // This browser does not have the minimum set of APIs we need.
     console.error('Browser not supported!');
@@ -99,10 +99,11 @@ function initApp() {
   window.addEventListener('offline', updateOnlineStatus);
 }
 
-function initPlayer() {
+async function initPlayer() {
   // Create a Player instance.
   const video = document.getElementById('video');
-  const player = new shaka.Player(video);
+  const player = new shaka.Player();
+  await player.attach(video);
 
   // Attach player and storage to the window to make it easy to access
   // in the JS console and so we can access it in other methods.
@@ -437,14 +438,14 @@ That’s it! For your convenience, here is the completed code:
 ```js
 // myapp.js
 
-function initApp() {
+async function initApp() {
   // Install built-in polyfills to patch browser incompatibilities.
   shaka.polyfill.installAll();
 
   // Check to see if the browser supports the basic APIs Shaka needs.
   if (shaka.Player.isBrowserSupported()) {
     // Everything looks good!
-    initPlayer();
+    await initPlayer();
   } else {
     // This browser does not have the minimum set of APIs we need.
     console.error('Browser not supported!');
@@ -457,10 +458,11 @@ function initApp() {
   window.addEventListener('offline', updateOnlineStatus);
 }
 
-function initPlayer() {
+async function initPlayer() {
   // Create a Player instance.
   const video = document.getElementById('video');
-  const player = new shaka.Player(video);
+  const player = new shaka.Player();
+  await player.attach(video);
 
   // Attach player and storage to the window to make it easy to access
   // in the JS console and so we can access it in other methods.

package/docs/tutorials/plugins.md

@@ -29,6 +29,7 @@ __Manifest parsers__
   - Default manifest parser plugins:
     - DASH: {@linksource shaka.dash.DashParser}
     - HLS: {@linksource shaka.hls.HlsParser}
+    - MSS: {@linksource shaka.mss.MssParser}
 
 __Subtitle/caption parsers__
   - Selected by MIME type
@@ -38,6 +39,10 @@ __Subtitle/caption parsers__
       {@linksource shaka.text.Mp4VttParser}
     - TTML: {@linksource shaka.text.TtmlTextParser} and
       {@linksource shaka.text.Mp4TtmlParser}
+    - SubRip (SRT): {@linksource shaka.text.SrtTextParser}
+    - LyRiCs (LRC): {@linksource shaka.text.LrcTextParser}
+    - SubStation Alpha (SSA, ASS): {@linksource shaka.text.SsaTextParser}
+    - SubViewer (SBV): {@linksource shaka.text.SbvTextParser}
 
 __Subtitle/caption displayers__
   - Configured at runtime on a Player instance

package/docs/tutorials/ui-customization.md

@@ -68,6 +68,8 @@ The following elements can be added to the UI bar using this configuration value
   supports AirPlay.
 * cast: adds a button that opens a Chromecast dialog. The button is visible only if there is
   at least one Chromecast device on the same network available for casting.
+* remote: adds a button that opens a Remote Playback dialog. The button is visible only if the
+  browser supports Remote Playback API.
 * quality: adds a button that controls enabling/disabling of abr and video resolution selection.
 * language: adds a button that controls audio language selection.
 * playback_rate: adds a button that controls the playback rate selection.
@@ -91,6 +93,8 @@ The following buttons can be added to the overflow menu:
 * playback_rate: adds a button that controls the playback rate selection.
 * airplay: adds a button that opens a AirPlay dialog. The button is visible only if the browser
   supports AirPlay.
+* remote: adds a button that opens a Remote Playback dialog. The button is visible only if the
+  browser supports Remote Playback API.
 * Statistics: adds a button that displays statistics of the video.
 <!-- TODO: If we add more buttons that can be put in the order this way, list them here. -->
 
@@ -184,6 +188,19 @@ const config = {
 ui.configure(config);
 ```
 
+If you've chosen to display chapters, you can specify the color for the chapter markers on
+the timeline and the text color of the chapter titles that popup on hover:
+ ```js
+const config = {
+  displayChapters: true,
+  seekBarColors: {
+    chapterMarks: 'rgb(27, 27, 27)',
+    chapterLabels: 'rgb(255, 255, 255)'
+  }
+}
+ui.configure(config);
+```
+
 #### Configuring playback, fast forward and rewind rates
 The rate in which the player can play, fast forward and rewind content can be configured using the `playbackRates`, `fastForwardRates` and `rewindRates` options.
 

package/docs/tutorials/ui.md

@@ -203,7 +203,8 @@ constructor.
 ```js
 // "local" because it is for local playback only, as opposed to the player proxy
 // object, which will route your calls to the ChromeCast receiver as necessary.
-const localPlayer = new shaka.Player(videoElement);
+const localPlayer = new shaka.Player();
+await localPlayer.attach(videoElement);
 // "Overlay" because the UI will add DOM elements inside the container,
 // to visually overlay the video element
 const ui = new shaka.ui.Overlay(localPlayer, videoContainerElement,

package/docs/tutorials/upgrade.md

@@ -99,3 +99,6 @@ application:
 
   - Plugin changes:
     - `Transmuxer` plugins now has three new parameters in `transmux()` method.
+
+  - Player API Changes:
+    - The constructor no longer takes `mediaElement` as a parameter; use the `attach` method to attach to a media element instead. (Deprecated in v4.6)

package/externs/css_style_declaration.js

@@ -0,0 +1,19 @@
+/*! @license
+ * Shaka Player
+ * Copyright 2016 Google LLC
+ * SPDX-License-Identifier: Apache-2.0
+ */
+
+
+/**
+ * @fileoverview Externs for CSSStyleDeclaration properties not in the
+ * Closure compiler.
+ *
+ * @externs
+ */
+
+
+/**
+ * @type {string}
+ */
+CSSStyleDeclaration.prototype.textCombineUpright;