CI Update

 Build.Reason:Manual by Peter Collins
 Build.Url:https://apidrop.visualstudio.com/Content%20CI/_build/results?buildId=488550&view=results
 source_repo.branch:dev/pjc/net-android-35
 source_repo.url:https://apidrop.visualstudio.com/_git/binaries

Author: [email protected]

docs/xml/Android.AccessibilityServices/AccessibilityService.xml

@@ -85,22 +85,19 @@
                 </intent-filter>
                 <meta-data android:name="android.accessibilityservice" android:resource="@xml/accessibilityservice" />
             &amp;lt;/service&amp;gt;</code>
-      <para>&lt;p class="note"&gt;
-            &lt;strong&gt;Note:&lt;/strong&gt; This approach enables setting all properties.
-            &lt;/p&gt;</para>
+      <para>&lt;strong&gt;Note:&lt;/strong&gt; This approach enables setting all properties.</para>
       <para>For more details refer to <c>#SERVICE_META_DATA</c> and
             <c>&amp;lt;{@link android.R.styleable#AccessibilityService accessibility-service}&amp;gt;</c>.</para>
       <para>&lt;/li&gt;
             &lt;li&gt;
             Calling <c>AccessibilityService#setServiceInfo(AccessibilityServiceInfo)</c>. Note
-            that this method can be called any time to dynamically change the service configuration.
-            &lt;p class="note"&gt;
-            &lt;strong&gt;Note:&lt;/strong&gt; This approach enables setting only dynamically configurable properties:
+            that this method can be called any time to dynamically change the service configuration.</para>
+      <para>&lt;strong&gt;Note:&lt;/strong&gt; This approach enables setting only dynamically configurable properties:
             <c>AccessibilityServiceInfo#eventTypes</c>,
             <c>AccessibilityServiceInfo#feedbackType</c>,
             <c>AccessibilityServiceInfo#flags</c>,
             <c>AccessibilityServiceInfo#notificationTimeout</c>,
-            <c>AccessibilityServiceInfo#packageNames</c>&lt;/p&gt;</para>
+            <c>AccessibilityServiceInfo#packageNames</c></para>
       <para>For more details refer to <c>AccessibilityServiceInfo</c>.</para>
       <para>&lt;/li&gt;
             &lt;/ul&gt;
@@ -115,13 +112,11 @@
             <c>AccessibilityService#findFocus(int)</c>,
             <c>AccessibilityService#getWindows()</c>, or
             <c>AccessibilityService#getRootInActiveWindow()</c>.</para>
-      <para>&lt;p class="note"&gt;
-            &lt;strong&gt;Note&lt;/strong&gt; An accessibility service may have requested to be notified for
+      <para>&lt;strong&gt;Note&lt;/strong&gt; An accessibility service may have requested to be notified for
             a subset of the event types, and thus be unaware when the node hierarchy has changed. It is also
             possible for a node to contain outdated information because the window content may change at any
-            time.
-            &lt;/p&gt;
-            &lt;h3&gt;Drawing Accessibility Overlays&lt;/h3&gt;</para>
+            time.</para>
+      <para>&lt;h3&gt;Drawing Accessibility Overlays&lt;/h3&gt;</para>
       <para>Accessibility services can draw overlays on top of existing screen contents.
             Accessibility overlays can be used to visually highlight items on the screen
             e.g. indicate the current item with accessibility focus.
@@ -144,12 +139,11 @@
       <para>&lt;h3&gt;Notification strategy&lt;/h3&gt;</para>
       <para>All accessibility services are notified of all events they have requested, regardless of their
             feedback type.</para>
-      <para>&lt;p class="note"&gt;
-            &lt;strong&gt;Note:&lt;/strong&gt; The event notification timeout is useful to avoid propagating
+      <para>&lt;strong&gt;Note:&lt;/strong&gt; The event notification timeout is useful to avoid propagating
             events to the client too frequently since this is accomplished via an expensive
             interprocess call. One can think of the timeout as a criteria to determine when
-            event generation has settled down.&lt;/p&gt;
-            &lt;h3&gt;Event types&lt;/h3&gt;
+            event generation has settled down.</para>
+      <para>&lt;h3&gt;Event types&lt;/h3&gt;
             &lt;ul&gt;
             &lt;li&gt;<c>AccessibilityEvent#TYPE_VIEW_CLICKED</c>&lt;/li&gt;
             &lt;li&gt;<c>AccessibilityEvent#TYPE_VIEW_LONG_CLICKED</c>&lt;/li&gt;

docs/xml/Android.Animation/AnimatorSet+Builder.xml

@@ -30,23 +30,23 @@
             intention of the <c>Builder</c> methods, along with the <c>AnimatorSet#play(Animator) play()</c> method of <c>AnimatorSet</c> is to make it possible
             to express the dependency relationships of animations in a natural way. Developers can also
             use the <c>AnimatorSet#playTogether(Animator[]) playTogether()</c> and <c>AnimatorSet#playSequentially(Animator[]) playSequentially()</c> methods if these suit the need,
-            but it might be easier in some situations to express the AnimatorSet of animations in pairs.
-            &lt;p/&gt;</para>
+            but it might be easier in some situations to express the AnimatorSet of animations in pairs.</para>
+      <para />
       <para>The <c>Builder</c> object cannot be constructed directly, but is rather constructed
             internally via a call to <c>AnimatorSet#play(Animator)</c>.</para>
-      <para>&lt;p/&gt;</para>
+      <para />
       <para>For example, this sets up a AnimatorSet to play anim1 and anim2 at the same time, anim3 to
             play when anim2 finishes, and anim4 to play when anim3 finishes:</para>
       <code lang="text/java">AnimatorSet s = new AnimatorSet();
                 s.play(anim1).with(anim2);
                 s.play(anim2).before(anim3);
                 s.play(anim4).after(anim3);
             </code>
-      <para>&lt;p/&gt;</para>
+      <para />
       <para>Note in the example that both <c>Builder#before(Animator)</c> and <c>Builder#after(Animator)</c> are used. These are just different ways of expressing the same
             relationship and are provided to make it easier to say things in a way that is more natural,
             depending on the situation.</para>
-      <para>&lt;p/&gt;</para>
+      <para />
       <para>It is possible to make several calls into the same <c>Builder</c> object to express
             multiple relationships. However, note that it is only the animation passed into the initial
             <c>AnimatorSet#play(Animator)</c> method that is the dependency in any of the successive
@@ -62,7 +62,7 @@
               s.play(anim1).before(anim2);
               s.play(anim2).before(anim3);
             </code>
-      <para>&lt;p/&gt;</para>
+      <para />
       <para>Note that it is possible to express relationships that cannot be resolved and will not
             result in sensible results. For example, <c>play(anim1).after(anim1)</c> makes no
             sense. In general, circular dependencies like this one (or more indirect ones where a depends

docs/xml/Android.App.Admin/DevicePolicyManager.xml

@@ -29,22 +29,19 @@
             apps running on the device.</para>
       <para>This class contains three types of methods:
             &lt;ol&gt;&lt;li&gt;Those aimed at managing apps&lt;li&gt;Those aimed at the Device Policy Management Role Holder&lt;li&gt;Those aimed at apps which wish to respect device policy&lt;/ol&gt;</para>
-      <para>The intended caller for each API is indicated in its Javadoc.
-            
-            &lt;p id="managingapps"&gt;&lt;b&gt;Managing Apps&lt;/b&gt;</para>
+      <para>The intended caller for each API is indicated in its Javadoc.</para>
+      <para>&lt;b&gt;Managing Apps&lt;/b&gt;</para>
       <para>Apps can be made capable of setting device policy ("Managing Apps") either by
             being set as a Device Administrator, being set as a
             Device Policy Controller, or by holding the
-            appropriate Permissions.
-            
-            &lt;p id="deviceadmin"&gt;A &lt;b&gt;Device Administrator&lt;/b&gt; is an app which is able to enforce device
+            appropriate Permissions.</para>
+      <para>A &lt;b&gt;Device Administrator&lt;/b&gt; is an app which is able to enforce device
             policies that it has declared in its device admin XML file. An app can prompt the user to give it
             device administator privileges using the <c>#ACTION_ADD_DEVICE_ADMIN</c> action.</para>
       <para>For more information about Device Administration, read the
             <see href="https://developer.android.com/guide/topics/admin/device-admin.html">Device Administration</see>
-            developer guide.
-            
-            &lt;p id="devicepolicycontroller"&gt;Through Managed Provisioning,
+            developer guide.</para>
+      <para>Through Managed Provisioning,
             Device Administrator apps can also be recognised as &lt;b&gt;
              Device Policy Controllers&lt;/b&gt;. Device Policy Controllers can be one of
             two types:
@@ -74,35 +71,30 @@
             Controller</see>.</para>
       <para>Permissions are generally only given to apps
             fulfilling particular key roles on the device (such as managing <c>DeviceLockManager
-            device locks</c>).
-            
-            &lt;p id="roleholder"&gt;&lt;b&gt;Device Policy Management Role Holder&lt;/b&gt;</para>
+            device locks</c>).</para>
+      <para>&lt;b&gt;Device Policy Management Role Holder&lt;/b&gt;</para>
       <para>One app on the device fulfills the <c>RoleManager#ROLE_DEVICE_POLICY_MANAGEMENT Device
             Policy Management Role</c> and is trusted with managing the overall state of
             Device Policy. This has access to much more powerful methods than
-            managing apps.
-            
-            &lt;p id="querying"&gt;&lt;b&gt;Querying Device Policy&lt;/b&gt;</para>
+            managing apps.</para>
+      <para>&lt;b&gt;Querying Device Policy&lt;/b&gt;</para>
       <para>In most cases, regular apps do not need to concern themselves with device
             policy, and restrictions will be enforced automatically. There are some cases
             where an app may wish to query device policy to provide a better user
             experience. Only a small number of policies allow apps to query them directly.
-            These APIs will typically have no special required permissions.
-            
-            &lt;p id="managedprovisioning"&gt;&lt;b&gt;Managed Provisioning&lt;/b&gt;</para>
+            These APIs will typically have no special required permissions.</para>
+      <para>&lt;b&gt;Managed Provisioning&lt;/b&gt;</para>
       <para>Managed Provisioning is the process of recognising an app as a
             Profile Owner. It
             involves presenting education and consent screens to the user to ensure they
             are aware of the capabilities this grants the Device Policy
             Controller</para>
       <para>For more information on provisioning, see <see href="https://developer.android.com/work/dpc/build-dpc">Building a
-            Device Policy Controller</see>.
-            
-            &lt;p id="managed_profile"&gt;A &lt;b&gt;Managed Profile&lt;/b&gt; enables data separation. For example to use
+            Device Policy Controller</see>.</para>
+      <para>A &lt;b&gt;Managed Profile&lt;/b&gt; enables data separation. For example to use
             a device both for personal and corporate usage. The managed profile and its
-            <c>UserManager#getProfileParent parent</c> share a launcher.
-            
-            &lt;p id="affiliated"&gt;&lt;b&gt;Affiliation&lt;/b&gt;</para>
+            <c>UserManager#getProfileParent parent</c> share a launcher.</para>
+      <para>&lt;b&gt;Affiliation&lt;/b&gt;</para>
       <para>Using the <c>#setAffiliationIds</c> method, a
             Device Owner can set a list of affiliation ids for the
             <c>UserManager#isSystemUser System User</c>. Any Profile Owner on
@@ -116,22 +108,19 @@
             that of the Device Owner. It also allows use of the
             <c>#bindDeviceAdminServiceAsUser</c> APIs for direct communication between the
             Device Owner and
-            affiliated Profile Owners.
-            
-            &lt;p id="organization-owned"&gt;&lt;b&gt;Organization Owned&lt;/b&gt;</para>
+            affiliated Profile Owners.</para>
+      <para>&lt;b&gt;Organization Owned&lt;/b&gt;</para>
       <para>An organization owned device is one which is not owned by the person making use of the device and
             is instead owned by an organization such as their employer or education provider. These devices
             are recognised as being organization owned either by the presence of a
             device owner or of a
             <c>#isOrganizationOwnedDeviceWithManagedProfile profile which has a profile owner is marked
-            as organization owned</c>.
-            
-            &lt;p id="profile-on-parent-organization-owned"&gt;Profile owners running on an
+            as organization owned</c>.</para>
+      <para>Profile owners running on an
             organization owned device can exercise additional capabilities
             using the <c>#getParentProfileInstance(ComponentName)</c> API which apply to the parent user.
-            Each API will indicate if it is usable in this way.
-            
-            &lt;p id="automotive"&gt;&lt;b&gt;Android Automotive&lt;/b&gt;</para>
+            Each API will indicate if it is usable in this way.</para>
+      <para>&lt;b&gt;Android Automotive&lt;/b&gt;</para>
       <para>On <c>android.content.pm.PackageManager#FEATURE_AUTOMOTIVE
             "Android Automotive builds"</c>, some methods can throw
             <c>UnsafeStateException "an exception"</c> if an action is unsafe (for example, if the vehicle
@@ -351,10 +340,9 @@
         <remarks>
           <para>Broadcast Action: Sent after application delegation scopes are changed. The new delegation
             scopes will be sent in an <c>ArrayList&lt;String&gt;</c> extra identified by the
-            <c>#EXTRA_DELEGATION_SCOPES</c> key.
-            
-            &lt;p class="note"&gt;&lt;b&gt;Note:&lt;/b&gt; This is a protected intent that can only be sent by the
-            system.&lt;/p&gt;</para>
+            <c>#EXTRA_DELEGATION_SCOPES</c> key.</para>
+          <para>&lt;b&gt;Note:&lt;/b&gt; This is a protected intent that can only be sent by the
+            system.</para>
           <para>
             <format type="text/html">
               <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager#ACTION_APPLICATION_DELEGATION_SCOPES_CHANGED" title="Reference documentation">Java documentation for <code>android.app.admin.DevicePolicyManager.ACTION_APPLICATION_DELEGATION_SCOPES_CHANGED</code>.</a>
@@ -12461,7 +12449,8 @@
             A device owner app is a special device admin that cannot be deactivated by the user, once
             activated as a device admin. It also cannot be uninstalled. To check whether a particular
             package is currently registered as the device owner app, pass in the package name from
-            <c>Context#getPackageName()</c> to this method.&lt;p/&gt;This is useful for device
+            <c>Context#getPackageName()</c> to this method.</para>
+          <para>This is useful for device
             admin apps that want to check whether they are also registered as the device owner app. The
             exact mechanism by which a device admin app is registered as a device owner app is defined by
             the setup process.</para>
@@ -22223,20 +22212,16 @@
             cannot manage it through the UI, and <c>#PERMISSION_GRANT_STATE_GRANTED granted</c> in which
             the permission is granted and the user cannot manage it through the UI. This method can only
             be called by a profile owner, device owner, or a delegate given the
-            <c>#DELEGATION_PERMISSION_GRANT</c> scope via <c>#setDelegatedScopes</c>.
-            &lt;p/&gt;
-            Note that user cannot manage other permissions in the affected group through the UI
+            <c>#DELEGATION_PERMISSION_GRANT</c> scope via <c>#setDelegatedScopes</c>.</para>
+          <para>Note that user cannot manage other permissions in the affected group through the UI
             either and their granted state will be kept as the current value. Thus, it's recommended that
-            you set the grant state of all the permissions in the affected group.
-            &lt;p/&gt;
-            Setting the grant state to <c>#PERMISSION_GRANT_STATE_DEFAULT default</c> does not revoke
-            the permission. It retains the previous grant, if any.
-            &lt;p/&gt;
-            Device admins with a <c>targetSdkVersion</c> &amp;lt; <c>android.os.Build.VERSION_CODES#Q</c>
+            you set the grant state of all the permissions in the affected group.</para>
+          <para>Setting the grant state to <c>#PERMISSION_GRANT_STATE_DEFAULT default</c> does not revoke
+            the permission. It retains the previous grant, if any.</para>
+          <para>Device admins with a <c>targetSdkVersion</c> &amp;lt; <c>android.os.Build.VERSION_CODES#Q</c>
             cannot grant and revoke permissions for applications built with a <c>targetSdkVersion</c>
-            &amp;lt; <c>android.os.Build.VERSION_CODES#M</c>.
-            &lt;p/&gt;
-            Admins with a <c>targetSdkVersion</c> &amp;ge; <c>android.os.Build.VERSION_CODES#Q</c> can
+            &amp;lt; <c>android.os.Build.VERSION_CODES#M</c>.</para>
+          <para>Admins with a <c>targetSdkVersion</c> &amp;ge; <c>android.os.Build.VERSION_CODES#Q</c> can
             grant and revoke permissions of all apps. Similar to the user revoking a permission from a
             application built with a <c>targetSdkVersion</c> &amp;lt;
             <c>android.os.Build.VERSION_CODES#M</c> the app-op matching the permission is set to
@@ -22338,9 +22323,8 @@
             can allow automatic granting or denying of runtime permission requests by an application.
             This also applies to new permissions declared by app updates. When a permission is denied or
             granted this way, the effect is equivalent to setting the permission * grant state via
-            <c>#setPermissionGrantState</c>.
-            &lt;p/&gt;
-            As this policy only acts on runtime permission requests, it only applies to applications
+            <c>#setPermissionGrantState</c>.</para>
+          <para>As this policy only acts on runtime permission requests, it only applies to applications
             built with a <c>targetSdkVersion</c> of <c>android.os.Build.VERSION_CODES#M</c> or later.</para>
           <para>NOTE: On devices running <c>android.os.Build.VERSION_CODES#S</c> and above, an auto-grant
             policy will not apply to certain sensors-related permissions on some configurations.
@@ -22960,9 +22944,8 @@
             local or remote administrator of the user.</summary>
         <remarks>
           <para>Designates a specific service component as the provider for making permission requests of a
-            local or remote administrator of the user.
-            &lt;p/&gt;
-            Only a device owner or profile owner can designate the restrictions provider.</para>
+            local or remote administrator of the user.</para>
+          <para>Only a device owner or profile owner can designate the restrictions provider.</para>
           <para>
             <format type="text/html">
               <a href="https://developer.android.com/reference/android/app/admin/DevicePolicyManager#setRestrictionsProvider(android.content.ComponentName,%20android.content.ComponentName)" title="Reference documentation">Java documentation for <code>android.app.admin.DevicePolicyManager.setRestrictionsProvider(android.content.ComponentName, android.content.ComponentName)</code>.</a>