From 4ba7fd0ace3c4a15baa01019023e1a0d42453b96 Mon Sep 17 00:00:00 2001 From: jbibik Date: Thu, 18 Jul 2024 08:32:10 -0700 Subject: [PATCH] Fix javadoc formatting from backticks to tags PiperOrigin-RevId: 653629763 --- .../main/java/androidx/media3/exoplayer/ExoPlayer.java | 10 +++++----- .../media3/exoplayer/offline/DownloadManager.java | 4 ++-- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/libraries/exoplayer/src/main/java/androidx/media3/exoplayer/ExoPlayer.java b/libraries/exoplayer/src/main/java/androidx/media3/exoplayer/ExoPlayer.java index 9433a68002..d4b75b3184 100644 --- a/libraries/exoplayer/src/main/java/androidx/media3/exoplayer/ExoPlayer.java +++ b/libraries/exoplayer/src/main/java/androidx/media3/exoplayer/ExoPlayer.java @@ -140,11 +140,11 @@ import java.util.List; * otherwise. For the vast majority of cases this should be the application's main thread. * Using the application's main thread is also a requirement when using ExoPlayer's UI * components or the IMA extension. The thread on which an ExoPlayer instance must be accessed - * can be explicitly specified by passing a `Looper` when creating the player. If no `Looper` - * is specified, then the `Looper` of the thread that the player is created on is used, or if - * that thread does not have a `Looper`, the `Looper` of the application's main thread is - * used. In all cases the `Looper` of the thread from which the player must be accessed can be - * queried using {@link #getApplicationLooper()}. + * can be explicitly specified by passing a {@link Looper} when creating the player. If no + * {@code Looper} is specified, then the {@code Looper} of the thread that the player is + * created on is used, or if that thread does not have a {@code Looper}, the {@code Looper} of + * the application's main thread is used. In all cases the {@code Looper} of the thread from + * which the player must be accessed can be queried using {@link #getApplicationLooper()}. *
  • Registered listeners are called on the thread associated with {@link * #getApplicationLooper()}. Note that this means registered listeners are called on the same * thread which must be used to access the player. diff --git a/libraries/exoplayer/src/main/java/androidx/media3/exoplayer/offline/DownloadManager.java b/libraries/exoplayer/src/main/java/androidx/media3/exoplayer/offline/DownloadManager.java index 02a7745f08..6514df14f2 100644 --- a/libraries/exoplayer/src/main/java/androidx/media3/exoplayer/offline/DownloadManager.java +++ b/libraries/exoplayer/src/main/java/androidx/media3/exoplayer/offline/DownloadManager.java @@ -67,8 +67,8 @@ import java.util.concurrent.Executor; *

    A download manager instance must be accessed only from the thread that created it, unless that * thread does not have a {@link Looper}. In that case, it must be accessed only from the * application's main thread. Registered listeners will be called on the same thread. In all cases - * the `Looper` of the thread from which the manager must be accessed can be queried using {@link - * #getApplicationLooper()}. + * the {@code Looper} of the thread from which the manager must be accessed can be queried using + * {@link #getApplicationLooper()}. */ @UnstableApi public final class DownloadManager {