From c1573106fabc40aa294dc040997b687aac239a2c Mon Sep 17 00:00:00 2001
From: ibaker <ibaker@google.com>
Date: Tue, 10 Dec 2019 16:42:33 +0000
Subject: [PATCH] Fix javadoc warnings exposed by -Xdoclint

PiperOrigin-RevId: 284776943
---
 .../google/android/exoplayer2/ExoPlayer.java  |  4 +-
 .../google/android/exoplayer2/Renderer.java   |  3 +-
 .../google/android/exoplayer2/Timeline.java   | 50 +++++++++----------
 .../trackselection/TrackSelector.java         |  2 -
 4 files changed, 29 insertions(+), 30 deletions(-)

diff --git a/library/core/src/main/java/com/google/android/exoplayer2/ExoPlayer.java b/library/core/src/main/java/com/google/android/exoplayer2/ExoPlayer.java
index f02ec3dd43..0374c04cb3 100644
--- a/library/core/src/main/java/com/google/android/exoplayer2/ExoPlayer.java
+++ b/library/core/src/main/java/com/google/android/exoplayer2/ExoPlayer.java
@@ -93,8 +93,8 @@ import com.google.android.exoplayer2.video.MediaCodecVideoRenderer;
  *
  * <p>The figure below shows ExoPlayer's threading model.
  *
- * <p align="center"><img src="doc-files/exoplayer-threading-model.svg" alt="ExoPlayer's threading
- * model">
+ * <p style="align:center"><img src="doc-files/exoplayer-threading-model.svg" alt="ExoPlayer's
+ * threading model">
  *
  * <ul>
  *   <li>ExoPlayer instances must be accessed from a single application thread. For the vast
diff --git a/library/core/src/main/java/com/google/android/exoplayer2/Renderer.java b/library/core/src/main/java/com/google/android/exoplayer2/Renderer.java
index 9e44e3741c..b699162e2f 100644
--- a/library/core/src/main/java/com/google/android/exoplayer2/Renderer.java
+++ b/library/core/src/main/java/com/google/android/exoplayer2/Renderer.java
@@ -32,7 +32,8 @@ import java.lang.annotation.RetentionPolicy;
  * valid state transitions are shown below, annotated with the methods that are called during each
  * transition.
  *
- * <p align="center"><img src="doc-files/renderer-states.svg" alt="Renderer state transitions">
+ * <p style="align:center"><img src="doc-files/renderer-states.svg" alt="Renderer state
+ * transitions">
  */
 public interface Renderer extends PlayerMessage.Target {
 
diff --git a/library/core/src/main/java/com/google/android/exoplayer2/Timeline.java b/library/core/src/main/java/com/google/android/exoplayer2/Timeline.java
index f99c4f47e0..93a87da0dc 100644
--- a/library/core/src/main/java/com/google/android/exoplayer2/Timeline.java
+++ b/library/core/src/main/java/com/google/android/exoplayer2/Timeline.java
@@ -45,7 +45,7 @@ import com.google.android.exoplayer2.util.Util;
  *
  * <h3 id="single-file">Single media file or on-demand stream</h3>
  *
- * <p align="center"><img src="doc-files/timeline-single-file.svg" alt="Example timeline for a
+ * <p style="align:center"><img src="doc-files/timeline-single-file.svg" alt="Example timeline for a
  * single file"> A timeline for a single media file or on-demand stream consists of a single period
  * and window. The window spans the whole period, indicating that all parts of the media are
  * available for playback. The window's default position is typically at the start of the period
@@ -53,17 +53,17 @@ import com.google.android.exoplayer2.util.Util;
  *
  * <h3>Playlist of media files or on-demand streams</h3>
  *
- * <p align="center"><img src="doc-files/timeline-playlist.svg" alt="Example timeline for a playlist
- * of files"> A timeline for a playlist of media files or on-demand streams consists of multiple
- * periods, each with its own window. Each window spans the whole of the corresponding period, and
- * typically has a default position at the start of the period. The properties of the periods and
- * windows (e.g. their durations and whether the window is seekable) will often only become known
- * when the player starts buffering the corresponding file or stream.
+ * <p style="align:center"><img src="doc-files/timeline-playlist.svg" alt="Example timeline for a
+ * playlist of files"> A timeline for a playlist of media files or on-demand streams consists of
+ * multiple periods, each with its own window. Each window spans the whole of the corresponding
+ * period, and typically has a default position at the start of the period. The properties of the
+ * periods and windows (e.g. their durations and whether the window is seekable) will often only
+ * become known when the player starts buffering the corresponding file or stream.
  *
  * <h3 id="live-limited">Live stream with limited availability</h3>
  *
- * <p align="center"><img src="doc-files/timeline-live-limited.svg" alt="Example timeline for a live
- * stream with limited availability"> A timeline for a live stream consists of a period whose
+ * <p style="align:center"><img src="doc-files/timeline-live-limited.svg" alt="Example timeline for
+ * a live stream with limited availability"> A timeline for a live stream consists of a period whose
  * duration is unknown, since it's continually extending as more content is broadcast. If content
  * only remains available for a limited period of time then the window may start at a non-zero
  * position, defining the region of content that can still be played. The window will have {@link
@@ -73,24 +73,24 @@ import com.google.android.exoplayer2.util.Util;
  *
  * <h3>Live stream with indefinite availability</h3>
  *
- * <p align="center"><img src="doc-files/timeline-live-indefinite.svg" alt="Example timeline for a
- * live stream with indefinite availability"> A timeline for a live stream with indefinite
+ * <p style="align:center"><img src="doc-files/timeline-live-indefinite.svg" alt="Example timeline
+ * for a live stream with indefinite availability"> A timeline for a live stream with indefinite
  * availability is similar to the <a href="#live-limited">Live stream with limited availability</a>
  * case, except that the window starts at the beginning of the period to indicate that all of the
  * previously broadcast content can still be played.
  *
  * <h3 id="live-multi-period">Live stream with multiple periods</h3>
  *
- * <p align="center"><img src="doc-files/timeline-live-multi-period.svg" alt="Example timeline for a
- * live stream with multiple periods"> This case arises when a live stream is explicitly divided
- * into separate periods, for example at content boundaries. This case is similar to the <a
+ * <p style="align:center"><img src="doc-files/timeline-live-multi-period.svg" alt="Example timeline
+ * for a live stream with multiple periods"> This case arises when a live stream is explicitly
+ * divided into separate periods, for example at content boundaries. This case is similar to the <a
  * href="#live-limited">Live stream with limited availability</a> case, except that the window may
  * span more than one period. Multiple periods are also possible in the indefinite availability
  * case.
  *
  * <h3>On-demand stream followed by live stream</h3>
  *
- * <p align="center"><img src="doc-files/timeline-advanced.svg" alt="Example timeline for an
+ * <p style="align:center"><img src="doc-files/timeline-advanced.svg" alt="Example timeline for an
  * on-demand stream followed by a live stream"> This case is the concatenation of the <a
  * href="#single-file">Single media file or on-demand stream</a> and <a href="#multi-period">Live
  * stream with multiple periods</a> cases. When playback of the on-demand stream ends, playback of
@@ -98,10 +98,10 @@ import com.google.android.exoplayer2.util.Util;
  *
  * <h3 id="single-file-midrolls">On-demand stream with mid-roll ads</h3>
  *
- * <p align="center"><img src="doc-files/timeline-single-file-midrolls.svg" alt="Example timeline
- * for an on-demand stream with mid-roll ad groups"> This case includes mid-roll ad groups, which
- * are defined as part of the timeline's single period. The period can be queried for information
- * about the ad groups and the ads they contain.
+ * <p style="align:center"><img src="doc-files/timeline-single-file-midrolls.svg" alt="Example
+ * timeline for an on-demand stream with mid-roll ad groups"> This case includes mid-roll ad groups,
+ * which are defined as part of the timeline's single period. The period can be queried for
+ * information about the ad groups and the ads they contain.
  */
 public abstract class Timeline {
 
@@ -112,7 +112,7 @@ public abstract class Timeline {
    * shows some of the information defined by a window, as well as how this information relates to
    * corresponding {@link Period Periods} in the timeline.
    *
-   * <p align="center"><img src="doc-files/timeline-window.svg" alt="Information defined by a
+   * <p style="align:center"><img src="doc-files/timeline-window.svg" alt="Information defined by a
    * timeline window">
    */
   public static final class Window {
@@ -327,12 +327,12 @@ public abstract class Timeline {
    * Holds information about a period in a {@link Timeline}. A period defines a single logical piece
    * of media, for example a media file. It may also define groups of ads inserted into the media,
    * along with information about whether those ads have been loaded and played.
-   * <p>
-   * The figure below shows some of the information defined by a period, as well as how this
+   *
+   * <p>The figure below shows some of the information defined by a period, as well as how this
    * information relates to a corresponding {@link Window} in the timeline.
-   * <p align="center">
-   *   <img src="doc-files/timeline-period.svg" alt="Information defined by a period">
-   * </p>
+   *
+   * <p style="align:center"><img src="doc-files/timeline-period.svg" alt="Information defined by a
+   * period">
    */
   public static final class Period {
 
diff --git a/library/core/src/main/java/com/google/android/exoplayer2/trackselection/TrackSelector.java b/library/core/src/main/java/com/google/android/exoplayer2/trackselection/TrackSelector.java
index fb74bd9d54..bc6cf14371 100644
--- a/library/core/src/main/java/com/google/android/exoplayer2/trackselection/TrackSelector.java
+++ b/library/core/src/main/java/com/google/android/exoplayer2/trackselection/TrackSelector.java
@@ -36,8 +36,6 @@ import com.google.android.exoplayer2.util.Assertions;
  *
  * The following interactions occur between the player and its track selector during playback.
  *
- * <p>
- *
  * <ul>
  *   <li>When the player is created it will initialize the track selector by calling {@link
  *       #init(InvalidationListener, BandwidthMeter)}.