@arcgis/map-components 4.34.0-next.133 → 4.34.0-next.135

package/dist/docs/docs.json

@@ -1,8 +1,8 @@
 {
-  "timestamp": "2025-09-16T04:37:43",
+  "timestamp": "2025-09-18T04:40:34",
   "compiler": {
     "name": "@arcgis/lumina-compiler",
-    "version": "4.34.0-next.133",
+    "version": "4.34.0-next.135",
     "typescriptVersion": "5.8.3"
   },
   "components": [
@@ -61,7 +61,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -237,7 +237,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The ViewModel's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-AreaMeasurement2D-AreaMeasurement2DViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -386,7 +386,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-AreaMeasurement2D.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisAreaMeasurement2d component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -910,7 +910,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisAreaMeasurement3d component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -1392,7 +1392,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -1546,7 +1546,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The current state of the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Attachments-AttachmentsViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -2045,7 +2045,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-BasemapGallery-BasemapGalleryViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -2095,7 +2095,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view from which the Basemap Gallery will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-BasemapGallery-BasemapGalleryViewModel.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBasemapGallery component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -2661,7 +2661,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -3118,7 +3118,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-BasemapLayerList-BasemapLayerListViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -3164,7 +3164,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-BasemapLayerList.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBasemapLayerList component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -3640,7 +3640,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-BasemapToggle-BasemapToggleViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -3690,7 +3690,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view from which the component or widget will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-BasemapToggle-BasemapToggleViewModel.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBasemapToggle component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -4565,7 +4565,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Bookmarks-BookmarksViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -4634,7 +4634,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view from which the widget will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Bookmarks-BookmarksViewModel.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBookmarks component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -4973,8 +4973,13 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the component. Typically used when the component is controlled by another component (e.g. by the Expand component).\n\nSee also: [Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)",
-          "docsTags": [],
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
+          "docsTags": [
+            {
+              "name": "see",
+              "text": "[Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)"
+            }
+          ],
           "default": "\"organization\"",
           "values": [
             {
@@ -5248,7 +5253,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A reference to the [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-BuildingExplorer.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisBuildingExplorer component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -5633,7 +5638,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -6020,7 +6025,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CatalogLayerList-CatalogLayerListViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -6066,7 +6071,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CatalogLayerList.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisCatalogLayerList component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "default": "null",
           "values": [
@@ -6512,7 +6517,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Compass-CompassViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -6558,7 +6563,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view in which the Compass obtains and indicates camera\n[heading](https://developers.arcgis.com/javascript/latest/api-reference/esri-Camera.html#heading), using a (SceneView) or\n[rotation](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#rotation) (MapView).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Compass-CompassViewModel.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisCompass component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -6693,11 +6698,11 @@
       "overview": "",
       "readme": "",
       "usage": {},
-      "docs": "The Coordinate Conversion component provides a way to display user cursor position either as map coordinates or as any of several popular coordinate notations. Additionally, the component provides a way to convert user input coordinates into a [Point](https://developers.arcgis.com/javascript/latest/api-reference/esri-geometry-Point.html).",
+      "docs": "The CoordinateConversion component provides a way to display user cursor position either as map coordinates or\nas any of several popular coordinate notations.  Additionally, the component provides a way to convert\nuser input coordinates into a [point](https://developers.arcgis.com/javascript/latest/api-reference/esri-geometry-Point.html).\n\n\nSeveral common formats are included by default:\n* XY - Longitude, Latitude (WGS84)\n* MGRS - [Military Grid Reference System](https://earth-info.nga.mil/index.php?dir=coordsys&action=coordsys#mgrs)\n* UTM - [Universal Transverse Mercator](https://earth-info.nga.mil/index.php?dir=coordsys&action=coordsys#utm)\n* DD - Decimal Degrees\n* DDM - Degrees Decimal Minutes\n* DMS - Degrees Minutes Seconds\n* Basemap - X, Y in the coordinate system used by the current basemap in the units used by the basemap.\nWeb Mercator is the standard for Esri-provided basemaps.\n\nAdditional formats can be created by a developer and made available\nthrough the component",
       "docsTags": [
         {
-          "name": "since",
-          "text": "4.28"
+          "name": "example",
+          "text": "```tsx\n<arcgis-map item-id=\"45b3b2fb35e94ab09381d0caa0da5946\">\n  <arcgis-coordinate-conversion position=\"bottom-left\"></arcgis-coordinate-conversion>\n</arcgis-map>\n```"
         },
         {
           "name": "superclass",
@@ -6752,8 +6757,17 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A [Collection](https://developers.arcgis.com/javascript/latest/api-reference/esri-core-Collection.html) containing every [Conversion](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CoordinateConversion-support-Conversion.html)\nthat the widget is currently displaying.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CoordinateConversion.html#conversions)",
-          "docsTags": [],
+          "docs": "A [collection](https://developers.arcgis.com/javascript/latest/api-reference/esri-core-Collection.html) of conversions\nthat the component is currently displaying. Each row in the component displaying a coordinate is a conversion.",
+          "docsTags": [
+            {
+              "name": "type",
+              "text": "{Collection<Conversion>}"
+            },
+            {
+              "name": "example",
+              "text": "Conversions can be set with an array of strings where each string is a format's name\n```ts\ncoordinateConversionComponent.conversions = [\"mgrs\"];\n```"
+            }
+          ],
           "values": [],
           "optional": true,
           "required": false
@@ -6774,17 +6788,52 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "Describes the location of the coordinates currently displayed by the widget as a [Point](https://developers.arcgis.com/javascript/latest/api-reference/esri-geometry-Point.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CoordinateConversion.html#currentLocation)",
+          "docs": "Describes the location of the coordinates currently displayed by the component as a [Point](https://developers.arcgis.com/javascript/latest/api-reference/esri-geometry-Point.html).\nSetting this property will update all conversions.",
           "docsTags": [
             {
-              "name": "readonly",
-              "text": ""
+              "name": "type",
+              "text": "{Point}"
+            },
+            {
+              "name": "example",
+              "text": "Set the current location\n```ts\ncoordinateConversionComponent.currentLocation = { x: 77.0369, y: 38.9072, spatialReference: { wkid: 4326 } };\n```"
             }
           ],
           "values": [],
           "optional": true,
           "required": false
         },
+        {
+          "name": "expanded",
+          "type": "boolean",
+          "complexType": {
+            "original": "boolean",
+            "resolved": "boolean",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "expanded",
+          "reflectToAttr": true,
+          "docs": "Describes whether the  component is expanded or not. Can be set manually to expand or retract the component.",
+          "docsTags": [
+            {
+              "name": "type",
+              "text": "{boolean}"
+            },
+            {
+              "name": "example",
+              "text": "Expand the component\n```ts\ncoordinateConversionComponent.expanded = true;\n```"
+            }
+          ],
+          "default": "false",
+          "values": [
+            {
+              "type": "boolean"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
         {
           "name": "formats",
           "type": "Collection<Format>",
@@ -6806,8 +6855,21 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A [Collection](https://developers.arcgis.com/javascript/latest/api-reference/esri-core-Collection.html) containing every [Format](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CoordinateConversion-support-Format.html)\nthat the widget is capable of displaying.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CoordinateConversion.html#formats)",
-          "docsTags": [],
+          "docs": "A [collection](https://developers.arcgis.com/javascript/latest/api-reference/esri-core-Collection.html) containing every coordinate format\nthat the component is capable of displaying.\n\nThe default formats are `basemap`, `dd`, `ddm`, `dms`, `mgrs`, `usng`, `utm`, and `xy`.",
+          "docsTags": [
+            {
+              "name": "type",
+              "text": "{Collection<Format>}"
+            },
+            {
+              "name": "example",
+              "text": "Only show the \"xy\" format\n```ts\nconst coordinateConversionComponent = document.getElementsByTagName(\"arcgis-coordinate-conversion\")[0];\nconst toRemove = coordinateConversionComponent.formats.filter(format => format.name !== \"xy\");\ncoordinateConversionComponent.formats.removeMany(toRemove);\n```"
+            },
+            {
+              "name": "example",
+              "text": "Show every format except \"xy\"\n```ts\nconst coordinateConversionComponent = document.getElementsByTagName(\"arcgis-coordinate-conversion\")[0];\nconst toRemove = coordinateConversionComponent.formats.filter(format => format.name === \"xy\");\ncoordinateConversionComponent.formats.removeMany(toRemove);\n```"
+            }
+          ],
           "values": [],
           "optional": true,
           "required": false
@@ -6822,7 +6884,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "This function provides the ability to override either the\n[MapView goTo()](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#goTo) or\n[SceneView goTo()](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html#goTo) methods.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CoordinateConversion.html#goToOverride)",
+          "docs": "This function provides the ability to override either the\n[MapView goTo()](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#goTo) or\n[SceneView goTo()](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html#goTo) methods.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CoordinateConversion-CoordinateConversionViewModel.html#goToOverride)",
           "docsTags": [
             {
               "name": "since",
@@ -6835,20 +6897,50 @@
         },
         {
           "name": "headingLevel",
-          "type": "number",
+          "type": "1 | 2 | 3 | 4 | 5 | 6",
           "complexType": {
-            "original": "number",
-            "resolved": "number",
+            "original": "1 | 2 | 3 | 4 | 5 | 6",
+            "resolved": "1 | 2 | 3 | 4 | 5 | 6",
             "references": {}
           },
           "mutable": true,
           "attr": "heading-level",
           "reflectToAttr": false,
-          "docs": "Indicates the heading level to use for the coordinate input and coordinate settings headings.",
-          "docsTags": [],
+          "docs": "Indicates the heading level to use for the coordinate input and coordinate settings headings. By default,\nthese headings are rendered as level 4 headings (e.g. `<h4>Input coordinate</h4>`). Depending on the coordinate conversion component's\nplacement in your app, you may need to adjust this heading for proper semantics. This is important for meeting\naccessibility standards.",
+          "docsTags": [
+            {
+              "name": "type",
+              "text": "{number}"
+            },
+            {
+              "name": "example",
+              "text": "Coordinate conversion heading will render as an <h2>\n```ts\ncoordinateConversionComponent.headingLevel = 2;\n```ts"
+            }
+          ],
           "default": "4",
           "values": [
             {
+              "value": "1",
+              "type": "number"
+            },
+            {
+              "value": "2",
+              "type": "number"
+            },
+            {
+              "value": "3",
+              "type": "number"
+            },
+            {
+              "value": "4",
+              "type": "number"
+            },
+            {
+              "value": "5",
+              "type": "number"
+            },
+            {
+              "value": "6",
               "type": "number"
             }
           ],
@@ -6865,9 +6957,18 @@
           },
           "mutable": true,
           "attr": "hide-capture-button",
-          "reflectToAttr": false,
-          "docs": "",
-          "docsTags": [],
+          "reflectToAttr": true,
+          "docs": "Determines whether the capture button will be shown in the component",
+          "docsTags": [
+            {
+              "name": "type",
+              "text": "{boolean}"
+            },
+            {
+              "name": "example",
+              "text": "Hide the capture button\n```tsx\n<arcgis-map item-id=\"45b3b2fb35e94ab09381d0caa0da5946\">\n  <arcgis-coordinate-conversion hide-capture-button position=\"bottom-left\"></arcgis-coordinate-conversion>\n</arcgis-map>\n```"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -6887,9 +6988,18 @@
           },
           "mutable": true,
           "attr": "hide-expand-button",
-          "reflectToAttr": false,
-          "docs": "",
-          "docsTags": [],
+          "reflectToAttr": true,
+          "docs": "Determines whether the expand button will be shown in the component",
+          "docsTags": [
+            {
+              "name": "type",
+              "text": "{boolean}"
+            },
+            {
+              "name": "example",
+              "text": "Hide the capture button\n```tsx\n<arcgis-map item-id=\"45b3b2fb35e94ab09381d0caa0da5946\">\n  <arcgis-coordinate-conversion hide-expand-button position=\"bottom-left\"></arcgis-coordinate-conversion>\n</arcgis-map>\n```"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -6909,9 +7019,18 @@
           },
           "mutable": true,
           "attr": "hide-input-button",
-          "reflectToAttr": false,
-          "docs": "",
-          "docsTags": [],
+          "reflectToAttr": true,
+          "docs": "Determines whether the edit button will be shown in the component",
+          "docsTags": [
+            {
+              "name": "type",
+              "text": "{boolean}"
+            },
+            {
+              "name": "example",
+              "text": "Hide the edit button\n```tsx\n<arcgis-map item-id=\"45b3b2fb35e94ab09381d0caa0da5946\">\n  <arcgis-coordinate-conversion hide-edit-button position=\"bottom-left\"></arcgis-coordinate-conversion>\n</arcgis-map>\n```"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -6931,9 +7050,18 @@
           },
           "mutable": true,
           "attr": "hide-settings-button",
-          "reflectToAttr": false,
-          "docs": "",
-          "docsTags": [],
+          "reflectToAttr": true,
+          "docs": "Determines whether the settings button will be shown in the component",
+          "docsTags": [
+            {
+              "name": "type",
+              "text": "{boolean}"
+            },
+            {
+              "name": "example",
+              "text": "Hide the capture button\n```tsx\n<arcgis-map item-id=\"45b3b2fb35e94ab09381d0caa0da5946\">\n  <arcgis-coordinate-conversion hide-settings-button position=\"bottom-left\"></arcgis-coordinate-conversion>\n</arcgis-map>\n```"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -6954,13 +7082,8 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
-          "docsTags": [
-            {
-              "name": "see",
-              "text": "[Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)"
-            }
-          ],
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).\nSearch [Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/) for possible values.",
+          "docsTags": [],
           "default": "\"coordinate-system\"",
           "values": [
             {
@@ -6981,8 +7104,9 @@
           "mutable": true,
           "attr": "label",
           "reflectToAttr": false,
-          "docs": "The widget's default label.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CoordinateConversion.html#label)",
+          "docs": "The component's default label.",
           "docsTags": [],
+          "default": "\"Coordinate conversion\"",
           "values": [
             {
               "type": "string"
@@ -7022,8 +7146,17 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "This symbol is used to visualize the location currently described by the widget when `capture` mode\nis active.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CoordinateConversion.html#locationSymbol)",
-          "docsTags": [],
+          "docs": "This symbol is used to visualize the location currently described by the component when `capture` mode\nis active.\n\nThis property should be set to an Esri JS API point symbol, typically a [Simple Marker Symbol](https://developers.arcgis.com/javascript/latest/api-reference/esri-symbols-SimpleMarkerSymbol.html)",
+          "docsTags": [
+            {
+              "name": "type",
+              "text": "{SimpleMarkerSymbol}"
+            },
+            {
+              "name": "example",
+              "text": "Set the location symbol to be an 'x'\n```ts\nconst coordinateConversionComponent = document.getElementsByTagName(\"arcgis-coordinate-conversion\")[0];\ncoordinateConversionComponent.locationSymbol = { type: \"simple-marker\", style: \"x\" };\n```"
+            }
+          ],
           "values": [
             {
               "type": "CIMSymbol"
@@ -7051,9 +7184,18 @@
           },
           "mutable": true,
           "attr": "mode",
-          "reflectToAttr": false,
-          "docs": "Describes the current mode of the widget.",
-          "docsTags": [],
+          "reflectToAttr": true,
+          "docs": "Describes the current mode of the component.\n\n* While in `live` mode, the component will update as the cursor moves.\n* While in `capture` mode, the component will update on mouse click and display a graphic\nmarking the current location.",
+          "docsTags": [
+            {
+              "name": "type",
+              "text": "{\"live\" | \"capture\"}"
+            },
+            {
+              "name": "example",
+              "text": "Programmatically set the component to capture mode\n```ts\nconst coordinateConversionComponent = document.getElementsByTagName(\"arcgis-coordinate-conversion\")[0];\ncoordinateConversionComponent.mode = \"capture\";\n```"
+            }
+          ],
           "default": "\"live\"",
           "values": [
             {
@@ -7068,28 +7210,6 @@
           "optional": true,
           "required": false
         },
-        {
-          "name": "multipleConversionsDisabled",
-          "type": "boolean",
-          "complexType": {
-            "original": "boolean",
-            "resolved": "boolean",
-            "references": {}
-          },
-          "mutable": true,
-          "attr": "multiple-conversions-disabled",
-          "reflectToAttr": false,
-          "docs": "If this property is set to `false`, multiple conversions cannot be displayed.",
-          "docsTags": [],
-          "default": "false",
-          "values": [
-            {
-              "type": "boolean"
-            }
-          ],
-          "optional": true,
-          "required": false
-        },
         {
           "name": "orientation",
           "type": "\"auto\" | \"expand-down\" | \"expand-up\"",
@@ -7100,9 +7220,14 @@
           },
           "mutable": true,
           "attr": "orientation",
-          "reflectToAttr": false,
-          "docs": "Determines whether the widget should expand up or down.",
-          "docsTags": [],
+          "reflectToAttr": true,
+          "docs": "Determines whether the component should expand up or down.  If set to `auto`\nthe component will be oriented based on its position in the view.",
+          "docsTags": [
+            {
+              "name": "type",
+              "text": "{\"auto\" | \"expand-up\" | \"expand-down\"}"
+            }
+          ],
           "default": "\"auto\"",
           "values": [
             {
@@ -7131,10 +7256,10 @@
           },
           "mutable": true,
           "attr": "position",
-          "reflectToAttr": false,
+          "reflectToAttr": true,
           "docs": "",
           "docsTags": [],
-          "deprecation": "since 4.34, use [`slot`](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/slot) instead.",
+          "deprecation": "since 4.34, use `slot` instead.",
           "values": [
             {
               "value": "bottom-leading",
@@ -7227,6 +7352,33 @@
           "optional": true,
           "required": false
         },
+        {
+          "name": "singleConversion",
+          "type": "boolean",
+          "complexType": {
+            "original": "boolean",
+            "resolved": "boolean",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "single-conversion",
+          "reflectToAttr": true,
+          "docs": "If this property is set to `true`, only a single conversion can be displated.  For a simpler experience with only\none conversion at a time, this property can be set to `true`.",
+          "docsTags": [
+            {
+              "name": "type",
+              "text": "{boolean}"
+            }
+          ],
+          "default": "false",
+          "values": [
+            {
+              "type": "boolean"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
         {
           "name": "state",
           "type": "\"disabled\" | \"loading\" | \"ready\"",
@@ -7238,7 +7390,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CoordinateConversion-CoordinateConversionViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -7273,9 +7425,14 @@
           },
           "mutable": true,
           "attr": "storage-disabled",
-          "reflectToAttr": false,
-          "docs": "Unless this property is set to `false`, sessionStorage or localStorage (depending on [storageType](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CoordinateConversion.html#storageType))\nwill be used to hydrate and persist the Coordinate Conversion component's state.",
-          "docsTags": [],
+          "reflectToAttr": true,
+          "docs": "If this property is set to `true`, sessionStorage or localStorage (depending on [storageType](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CoordinateConversion.html#storageType))\nwill not be used to hydrate and persist the component's state.",
+          "docsTags": [
+            {
+              "name": "type",
+              "text": "{boolean}"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -7296,8 +7453,21 @@
           "mutable": true,
           "attr": "storage-type",
           "reflectToAttr": false,
-          "docs": "This property determines whether sessionStorage or localStorage will be used to store widget state.",
-          "docsTags": [],
+          "docs": "This property determines whether sessionStorage or localStorage will be used to store component's state.",
+          "docsTags": [
+            {
+              "name": "type",
+              "text": "{\"session\" | \"local\"}"
+            },
+            {
+              "name": "see",
+              "text": "[Window.sessionStorage](https://developer.mozilla.org/en-US/docs/Web/API/Window/sessionStorage)"
+            },
+            {
+              "name": "see",
+              "text": "[Window.localStorage](https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage)"
+            }
+          ],
           "default": "\"session\"",
           "values": [
             {
@@ -7333,7 +7503,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CoordinateConversion.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisCoordinateConversion component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -7407,10 +7577,10 @@
           "name": "reverseConvert",
           "returns": {
             "type": "Promise<Point | null | undefined>",
-            "docs": ""
+            "docs": "://developers.arcgis.com/javascript/latest/api-reference/esri-geometry-Point.html | nil>} When resolved, returns a [point](https://developers.arcgis.com/javascript/latest/api-reference/esri-geometry-Point.html)."
           },
           "complexType": {
-            "signature": "(coordinate: string, format: __esri.Format): Promise<__esri.Point | nullish>",
+            "signature": "(coordinate: string, format: Format): Promise<__esri.Point | nullish>",
             "parameters": [
               {
                 "name": "coordinate",
@@ -7442,7 +7612,7 @@
               }
             }
           },
-          "signature": "reverseConvert(coordinate: string, format: __esri.Format): Promise<__esri.Point | nullish>",
+          "signature": "reverseConvert(coordinate: string, format: Format): Promise<__esri.Point | nullish>",
           "parameters": [
             {
               "name": "coordinate",
@@ -7455,18 +7625,45 @@
               "docs": ""
             }
           ],
-          "docs": "",
-          "docsTags": []
+          "docs": "Attempt to convert a string into a [point](https://developers.arcgis.com/javascript/latest/api-reference/esri-geometry-Point.html).  The format of the\nstring must be specified.  A [collection](https://developers.arcgis.com/javascript/latest/api-reference/esri-core-Collection.html) of available formats can be\nobtained from the [formats](#formats) property.",
+          "docsTags": [
+            {
+              "name": "param",
+              "text": "coordinate - The coordinate string."
+            },
+            {
+              "name": "param",
+              "text": " ://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-CoordinateConversion-support-Format.html} format - Specifies the format of the input coordinate."
+            },
+            {
+              "name": "return",
+              "text": "://developers.arcgis.com/javascript/latest/api-reference/esri-geometry-Point.html | nil>} When resolved, returns a [point](https://developers.arcgis.com/javascript/latest/api-reference/esri-geometry-Point.html)."
+            }
+          ]
         }
       ],
       "events": [
+        {
+          "event": "arcgisConversionChange",
+          "detail": "void",
+          "bubbles": true,
+          "complexType": {
+            "original": "void",
+            "resolved": "void",
+            "references": {}
+          },
+          "cancelable": true,
+          "composed": true,
+          "docs": "",
+          "docsTags": []
+        },
         {
           "event": "arcgisPropertyChange",
-          "detail": "{ name: \"state\" | \"currentLocation\"; }",
+          "detail": "{ name: \"state\" | \"mode\" | \"expanded\" | \"currentLocation\"; }",
           "bubbles": true,
           "complexType": {
-            "original": "{ name: \"state\" | \"currentLocation\"; }",
-            "resolved": "{ name: \"state\" | \"currentLocation\"; }",
+            "original": "{ name: \"state\" | \"mode\" | \"expanded\" | \"currentLocation\"; }",
+            "resolved": "{ name: \"state\" | \"mode\" | \"expanded\" | \"currentLocation\"; }",
             "references": {}
           },
           "cancelable": true,
@@ -7622,7 +7819,7 @@
           "required": false
         },
         {
-          "name": "directShadowsEnabled",
+          "name": "directShadowsDisabled",
           "type": "boolean",
           "complexType": {
             "original": "boolean",
@@ -7630,7 +7827,7 @@
             "references": {}
           },
           "mutable": true,
-          "attr": "direct-shadows-enabled",
+          "attr": "direct-shadows-disabled",
           "reflectToAttr": false,
           "docs": "",
           "docsTags": [],
@@ -7902,10 +8099,10 @@
         },
         {
           "name": "localDate",
-          "type": "Date",
+          "type": "Date | number | string",
           "complexType": {
-            "original": "Date",
-            "resolved": "Date",
+            "original": "Date | number | string",
+            "resolved": "Date | number | string",
             "references": {
               "Date": {
                 "location": "import",
@@ -7915,10 +8112,21 @@
             }
           },
           "mutable": true,
+          "attr": "local-date",
           "reflectToAttr": false,
           "docs": "The calendar date in the timezone given by [utcOffset](#utcOffset).\n\nThis property should only be set once the widget and the view are initialized, for example,\nfrom within an event handler. To initialize the view with a specific date and time, set a\n[SunLighting](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-3d-environment-SunLighting.html) on the [SceneView.environment](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html#environment).",
           "docsTags": [],
-          "values": [],
+          "values": [
+            {
+              "type": "Date"
+            },
+            {
+              "type": "number"
+            },
+            {
+              "type": "string"
+            }
+          ],
           "optional": true,
           "required": false
         },
@@ -8677,7 +8885,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The state of the view model.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-DirectionalPad-DirectionalPadViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -8717,7 +8925,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view which the directional pad will control.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-DirectionalPad-DirectionalPadViewModel.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDirectionalPad component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -9032,7 +9240,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -9302,7 +9510,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The current state of the view model.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Directions-DirectionsViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -9452,7 +9660,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view from which the widget will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Directions.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDirections component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -10018,10 +10226,10 @@
         },
         {
           "name": "unitOptions",
-          "type": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+          "type": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
           "complexType": {
-            "original": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
-            "resolved": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+            "original": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
+            "resolved": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
             "references": {
               "Array": {
                 "location": "import",
@@ -10054,7 +10262,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDirectLineMeasurement3d component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -10567,10 +10775,10 @@
         },
         {
           "name": "unitOptions",
-          "type": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+          "type": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
           "complexType": {
-            "original": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
-            "resolved": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+            "original": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
+            "resolved": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
             "references": {
               "Array": {
                 "location": "import",
@@ -10608,7 +10816,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDirectLineMeasurement3d component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [
             {
               "name": "inheritedFrom",
@@ -10838,7 +11046,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -11014,7 +11222,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-DistanceMeasurement2D-DistanceMeasurement2DViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -11115,10 +11323,10 @@
         },
         {
           "name": "unitOptions",
-          "type": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+          "type": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
           "complexType": {
-            "original": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
-            "resolved": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+            "original": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
+            "resolved": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
             "references": {
               "Array": {
                 "location": "import",
@@ -11151,7 +11359,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-DistanceMeasurement2D.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisDistanceMeasurement2d component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -11596,7 +11804,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -11843,7 +12051,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The widget's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Editor-EditorViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -11984,7 +12192,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Editor.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisEditor component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -12648,8 +12856,13 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the component. Typically used when the component is controlled by another component (e.g. by the Expand component).\n\nSee also: [Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)",
-          "docsTags": [],
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
+          "docsTags": [
+            {
+              "name": "see",
+              "text": "[Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)"
+            }
+          ],
           "default": "\"altitude\"",
           "values": [
             {
@@ -12760,27 +12973,27 @@
         },
         {
           "name": "profiles",
-          "type": "Collection<ElevationProfileLineGround | ElevationProfileLineInput | ElevationProfileLineQuery | ElevationProfileLineView>",
+          "type": "Collection<ElevationProfileElevationProfileLineGround | ElevationProfileElevationProfileLineInput | ElevationProfileElevationProfileLineQuery | ElevationProfileLineView>",
           "complexType": {
-            "original": "Collection<ElevationProfileLineGround | ElevationProfileLineInput | ElevationProfileLineQuery | ElevationProfileLineView>",
-            "resolved": "Collection<ElevationProfileLineGround | ElevationProfileLineInput | ElevationProfileLineQuery | ElevationProfileLineView>",
+            "original": "Collection<ElevationProfileElevationProfileLineGround | ElevationProfileElevationProfileLineInput | ElevationProfileElevationProfileLineQuery | ElevationProfileLineView>",
+            "resolved": "Collection<ElevationProfileElevationProfileLineGround | ElevationProfileElevationProfileLineInput | ElevationProfileElevationProfileLineQuery | ElevationProfileLineView>",
             "references": {
               "Collection": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
               },
-              "ElevationProfileLineGround": {
+              "ElevationProfileElevationProfileLineGround": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
               },
-              "ElevationProfileLineInput": {
+              "ElevationProfileElevationProfileLineInput": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
               },
-              "ElevationProfileLineQuery": {
+              "ElevationProfileElevationProfileLineQuery": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
@@ -13018,10 +13231,10 @@
         },
         {
           "name": "unitOptions",
-          "type": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+          "type": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
           "complexType": {
-            "original": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
-            "resolved": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+            "original": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
+            "resolved": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
             "references": {
               "Array": {
                 "location": "import",
@@ -13059,7 +13272,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A reference to the [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html) or the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-ElevationProfile.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisElevationProfile component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -13674,32 +13887,32 @@
         },
         {
           "name": "profiles",
-          "type": "Collection<ElevationProfileGroundLine | ElevationProfileInputLine | ElevationProfileQueryLine | ElevationProfileSceneLine>",
+          "type": "Collection<ElevationProfileLineGround | ElevationProfileLineInput | ElevationProfileLineQuery | ElevationProfileLineScene>",
           "complexType": {
-            "original": "Collection<ElevationProfileGroundLine | ElevationProfileInputLine | ElevationProfileQueryLine | ElevationProfileSceneLine>",
-            "resolved": "Collection<ElevationProfileGroundLine | ElevationProfileInputLine | ElevationProfileQueryLine | ElevationProfileSceneLine>",
+            "original": "Collection<ElevationProfileLineGround | ElevationProfileLineInput | ElevationProfileLineQuery | ElevationProfileLineScene>",
+            "resolved": "Collection<ElevationProfileLineGround | ElevationProfileLineInput | ElevationProfileLineQuery | ElevationProfileLineScene>",
             "references": {
               "Collection": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
               },
-              "ElevationProfileGroundLine": {
+              "ElevationProfileLineGround": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
               },
-              "ElevationProfileInputLine": {
+              "ElevationProfileLineInput": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
               },
-              "ElevationProfileQueryLine": {
+              "ElevationProfileLineQuery": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
               },
-              "ElevationProfileSceneLine": {
+              "ElevationProfileLineScene": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
@@ -13996,10 +14209,10 @@
         },
         {
           "name": "unitOptionsDistance",
-          "type": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+          "type": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
           "complexType": {
-            "original": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
-            "resolved": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+            "original": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
+            "resolved": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
             "references": {
               "Array": {
                 "location": "import",
@@ -14018,10 +14231,10 @@
         },
         {
           "name": "unitOptionsElevation",
-          "type": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+          "type": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
           "complexType": {
-            "original": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
-            "resolved": "Array<\"meters\" | \"metric\" | \"imperial\" | \"millimeters\" | \"centimeters\" | \"decimeters\" | \"kilometers\" | \"inches\" | \"feet\" | \"yards\" | \"miles\" | \"nautical-miles\" | \"us-feet\">",
+            "original": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
+            "resolved": "Array<\"meters\" | \"metric\" | \"centimeters\" | \"decimeters\" | \"feet\" | \"inches\" | \"kilometers\" | \"millimeters\" | \"nautical-miles\" | \"us-feet\" | \"yards\" | \"miles\" | \"imperial\">",
             "references": {
               "Array": {
                 "location": "import",
@@ -14059,7 +14272,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisElevationProfileNext component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -14848,7 +15061,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Expand-ExpandViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -14890,7 +15103,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view in which the Expand is used.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Expand-ExpandViewModel.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisExpand component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -15106,7 +15319,12 @@
           "attr": "chart-animation-disabled",
           "reflectToAttr": false,
           "docs": "Disables chart animation within the component.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -15140,22 +15358,22 @@
         },
         {
           "name": "flowItems",
-          "type": "Collection<HTMLArcgisFeatureRelationshipElement | HTMLArcgisFeatureElement>",
+          "type": "Collection<HTMLArcgisFeatureElement | HTMLArcgisFeatureRelationshipElement>",
           "complexType": {
-            "original": "Collection<HTMLArcgisFeatureRelationshipElement | HTMLArcgisFeatureElement>",
-            "resolved": "Collection<HTMLArcgisFeatureRelationshipElement | HTMLArcgisFeatureElement>",
+            "original": "Collection<HTMLArcgisFeatureElement | HTMLArcgisFeatureRelationshipElement>",
+            "resolved": "Collection<HTMLArcgisFeatureElement | HTMLArcgisFeatureRelationshipElement>",
             "references": {
               "Collection": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
               },
-              "HTMLArcgisFeatureRelationshipElement": {
+              "HTMLArcgisFeatureElement": {
                 "location": "local",
                 "path": "index.js",
                 "id": "notImplemented"
               },
-              "HTMLArcgisFeatureElement": {
+              "HTMLArcgisFeatureRelationshipElement": {
                 "location": "local",
                 "path": "index.js",
                 "id": "notImplemented"
@@ -15164,8 +15382,13 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
-          "docsTags": [],
+          "docs": "A collection of flow items that are used to manage drill-in navigation.",
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "values": [],
           "optional": true,
           "required": false
@@ -15217,6 +15440,10 @@
           "reflectToAttr": false,
           "docs": "The title for the feature. This can be disabled by setting the [`hideHeading`](#hideHeading) property to `true`.",
           "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            },
             {
               "name": "see",
               "text": "[headingLevel](#headingLevel)"
@@ -15250,7 +15477,7 @@
           "mutable": true,
           "attr": "heading-level",
           "reflectToAttr": false,
-          "docs": "Indicates the heading level to use for the [title](#title) of the component.\nBy default, the title is rendered\nas a level 2 heading (e.g. `<h2>Title of content</h2>`). Depending on the component's placement\nin your app, you may need to adjust this heading for proper semantics. This is\nimportant for meeting accessibility standards.",
+          "docs": "Indicates the heading level to use for the [heading](#heading) of the component.\nBy default, the title is rendered\nas a level 2 heading (e.g. `<h2>Title of content</h2>`). Depending on the component's placement\nin your app, you may need to adjust this heading for proper semantics. This is\nimportant for meeting accessibility standards.",
           "docsTags": [
             {
               "name": "see",
@@ -15325,8 +15552,128 @@
           "attr": "hide-content",
           "reflectToAttr": false,
           "docs": "This property provides the ability to hide or show content within the component.",
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
+          "default": "false",
+          "values": [
+            {
+              "type": "boolean"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
+        {
+          "name": "hideContentAttachments",
+          "type": "boolean",
+          "complexType": {
+            "original": "boolean",
+            "resolved": "boolean",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "hide-content-attachments",
+          "reflectToAttr": false,
+          "docs": "Indicates whether to hide all [AttachmentsContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-AttachmentsContent.html).",
+          "docsTags": [],
+          "default": "false",
+          "deprecation": "since 4.34, use [`hideAttachmentsContent`](#hideAttachmentsContent) instead.",
+          "values": [
+            {
+              "type": "boolean"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
+        {
+          "name": "hideContentExpression",
+          "type": "boolean",
+          "complexType": {
+            "original": "boolean",
+            "resolved": "boolean",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "hide-content-expression",
+          "reflectToAttr": false,
+          "docs": "Indicates whether to hide all [ExpressionContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-ExpressionContent.html).",
+          "docsTags": [],
+          "default": "false",
+          "deprecation": "since 4.34, use [`hideExpressionContent`](#hideExpressionContent) instead.",
+          "values": [
+            {
+              "type": "boolean"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
+        {
+          "name": "hideContentFields",
+          "type": "boolean",
+          "complexType": {
+            "original": "boolean",
+            "resolved": "boolean",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "hide-content-fields",
+          "reflectToAttr": false,
+          "docs": "Indicates whether to hide all [FieldsContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-FieldsContent.html).",
           "docsTags": [],
           "default": "false",
+          "deprecation": "since 4.34, use [`hideFieldsContent`](#hideFieldsContent) instead.",
+          "values": [
+            {
+              "type": "boolean"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
+        {
+          "name": "hideContentMedia",
+          "type": "boolean",
+          "complexType": {
+            "original": "boolean",
+            "resolved": "boolean",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "hide-content-media",
+          "reflectToAttr": false,
+          "docs": "Indicates whether to hide all [MediaContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-MediaContent.html).",
+          "docsTags": [],
+          "default": "false",
+          "deprecation": "since 4.34, use [`hideMediaContent`](#hideMediaContent) instead.",
+          "values": [
+            {
+              "type": "boolean"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
+        {
+          "name": "hideContentText",
+          "type": "boolean",
+          "complexType": {
+            "original": "boolean",
+            "resolved": "boolean",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "hide-content-text",
+          "reflectToAttr": false,
+          "docs": "Indicates whether to hide all [TextContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-TextContent.html).",
+          "docsTags": [],
+          "default": "false",
+          "deprecation": "since 4.34, use [`hideTextContent`](#hideTextContent) instead.",
           "values": [
             {
               "type": "boolean"
@@ -15347,7 +15694,12 @@
           "attr": "hide-custom-content",
           "reflectToAttr": false,
           "docs": "This property provides the ability to hide or show [custom content](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-CustomContent.html) within the component.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -15413,7 +15765,12 @@
           "attr": "hide-heading",
           "reflectToAttr": false,
           "docs": "This property provides the ability to hide or show the component's [heading](#heading).",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -15445,6 +15802,29 @@
           "optional": true,
           "required": false
         },
+        {
+          "name": "hideLastEditInfo",
+          "type": "boolean",
+          "complexType": {
+            "original": "boolean",
+            "resolved": "boolean",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "hide-last-edit-info",
+          "reflectToAttr": false,
+          "docs": "Indicates whether to hide the title associated with the feature.",
+          "docsTags": [],
+          "default": "false",
+          "deprecation": "since 4.33, use [`hideLastEditedInfo`](#hideLastEditedInfo) instead.",
+          "values": [
+            {
+              "type": "boolean"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
         {
           "name": "hideMediaContent",
           "type": "boolean",
@@ -15489,6 +15869,29 @@
           "optional": true,
           "required": false
         },
+        {
+          "name": "hideTitle",
+          "type": "boolean",
+          "complexType": {
+            "original": "boolean",
+            "resolved": "boolean",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "hide-title",
+          "reflectToAttr": false,
+          "docs": "Indicates whether to hide the title associated with the feature.",
+          "docsTags": [],
+          "default": "false",
+          "deprecation": "since 4.34, use [`hideHeading`](#hideHeading) instead.",
+          "values": [
+            {
+              "type": "boolean"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
         {
           "name": "icon",
           "type": "string",
@@ -15526,8 +15929,12 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "Indicates whether the current FeatureViewModel's [graphic](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Feature-FeatureViewModel.html#graphic) resides in a non-spatial table.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Feature-FeatureViewModel.html#isFeatureFromTable)",
+          "docs": "Indicates whether the current graphic resides in a non-spatial table.",
           "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            },
             {
               "name": "readonly",
               "text": ""
@@ -15636,7 +16043,12 @@
           "mutable": true,
           "reflectToAttr": false,
           "docs": "Overwrite localized strings for this component.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "values": [],
           "optional": true,
           "required": false
@@ -15759,7 +16171,12 @@
           "attr": "show-relationship-content",
           "reflectToAttr": false,
           "docs": "This property provides the ability to hide or show [relationship content](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-RelationshipContent.html) within the component.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -15781,7 +16198,12 @@
           "attr": "show-utility-network-content",
           "reflectToAttr": false,
           "docs": "This property provides the ability to hide or show [utility network content](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-UtilityNetworkContent.html) within the component.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -15837,7 +16259,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Feature-FeatureViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -15877,7 +16299,7 @@
           "mutable": true,
           "attr": "time-zone",
           "reflectToAttr": false,
-          "docs": "Dates and times displayed in the component will be displayed in this time zone. By default this time zone is\ninherited from [MapView.timeZone](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#timeZone). When a MapView is not associated with the component,\nthen the property will fallback to the `system` time zone.\n\n**Possible Values**\n\nValue | Description |\n----- | ----------- |\nsystem  | Dates and times will be displayed in the timezone of the device or browser.\nunknown | Dates and time are not adjusted for any timezone.\nSpecified IANA timezone | Dates and times will be displayed in the specified IANA time zone. See [wikipedia - List of tz database time zones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).",
+          "docs": "Dates and times displayed in the component will be displayed in this time zone. By default this time zone is\ninherited from [MapView.timeZone](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#timeZone). When a MapView is not associated with the component,\nthen the property will fallback to the `system` time zone.\n\n**Possible Values**\n- `system`: Dates and times will be displayed in the timezone of the device or browser.\n- `unknown`: Dates and time are not adjusted for any timezone.\n- Specified IANA timezone: Dates and times will be displayed in the specified IANA time zone. See [wikipedia - List of tz database time zones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).",
           "docsTags": [],
           "values": [
             {
@@ -15908,7 +16330,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Feature-FeatureViewModel.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisFeature component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -16135,8 +16557,13 @@
           },
           "signature": "updateGeometry(): Promise<void>",
           "parameters": [],
-          "docs": "",
-          "docsTags": []
+          "docs": "Updates the geometry of the graphic.",
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ]
         }
       ],
       "events": [
@@ -16353,7 +16780,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon displayed in the widget's button.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -16573,7 +17000,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The widget's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-FeatureForm-FeatureFormViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -17997,7 +18424,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "The string value which indicates the displayed [icon](https://developers.arcgis.com/calcite-design-system/icons/).",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -18965,7 +19392,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The state of the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-FeatureTable.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -19307,7 +19734,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html), [LinkChartView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-LinkChartView.html), or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-FeatureTable.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisFeatureTable component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -20050,11 +20477,11 @@
         },
         {
           "event": "arcgisPropertyChange",
-          "detail": "{ name: \"state\" | \"size\" | \"effectiveSize\" | \"isQueryingOrSyncing\" | \"layerView\"; }",
+          "detail": "{ name: \"state\" | \"size\" | \"layerView\" | \"effectiveSize\" | \"isQueryingOrSyncing\"; }",
           "bubbles": true,
           "complexType": {
-            "original": "{ name: \"state\" | \"size\" | \"effectiveSize\" | \"isQueryingOrSyncing\" | \"layerView\"; }",
-            "resolved": "{ name: \"state\" | \"size\" | \"effectiveSize\" | \"isQueryingOrSyncing\" | \"layerView\"; }",
+            "original": "{ name: \"state\" | \"size\" | \"layerView\" | \"effectiveSize\" | \"isQueryingOrSyncing\"; }",
+            "resolved": "{ name: \"state\" | \"size\" | \"layerView\" | \"effectiveSize\" | \"isQueryingOrSyncing\"; }",
             "references": {}
           },
           "cancelable": true,
@@ -20284,7 +20711,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon displayed in the widget's button.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -20516,7 +20943,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The widget's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-FeatureTemplates-FeatureTemplatesViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -20710,7 +21137,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "[Collection](https://developers.arcgis.com/javascript/latest/api-reference/esri-core-Collection.html) of [action](https://developers.arcgis.com/javascript/latest/api-reference/esri-support-actions-ActionButton.html) or [action toggle](https://developers.arcgis.com/javascript/latest/api-reference/esri-support-actions-ActionToggle.html) objects displayed in the action bar.\nEach action may be executed by clicking the icon or image symbolizing them.\nBy default, every component has a `Zoom To` action styled with a magnifying glass icon.\nWhen this icon is clicked, the map zooms in four LODs and centers on the selected feature.\nThis default action can be removed by setting [`includeDefaultActions`](#includeDefaultActions) to `false`, or by setting the [overwriteActions](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html#overwriteActions) property to `true` in the [PopupTemplate](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html).\nThe order of each action is the order in which they appear in the actions [Collection](https://developers.arcgis.com/javascript/latest/api-reference/esri-core-Collection.html).\nThe [`arcgisTriggerAction`](#arcgisTriggerAction) event fires each time an action is clicked.\nActions are defined with the properties listed in the [ActionButton](https://developers.arcgis.com/javascript/latest/api-reference/esri-support-actions-ActionButton.html) or [ActionToggle](https://developers.arcgis.com/javascript/latest/api-reference/esri-support-actions-ActionToggle.html) class.",
+          "docs": "[Collection](https://developers.arcgis.com/javascript/latest/api-reference/esri-core-Collection.html) of [action](https://developers.arcgis.com/javascript/latest/api-reference/esri-support-actions-ActionButton.html) or [action toggle](https://developers.arcgis.com/javascript/latest/api-reference/esri-support-actions-ActionToggle.html) objects displayed in the action bar.\nEach action may be executed by clicking the icon or image symbolizing them.\nBy default, every component has a `Zoom To` action styled with a magnifying glass icon.\nWhen this icon is clicked, the map zooms in four LODs and centers on the selected feature.\nThis default action can be removed by setting [`includeDefaultActionsDisabled`](#includeDefaultActionsDisabled) to `true`, or by setting the [overwriteActions](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html#overwriteActions) property to `true` in the [PopupTemplate](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html).\nThe order of each action is the order in which they appear in the actions [Collection](https://developers.arcgis.com/javascript/latest/api-reference/esri-core-Collection.html).\nThe [`arcgisTriggerAction`](#arcgisTriggerAction) event fires each time an action is clicked.\nActions are defined with the properties listed in the [ActionButton](https://developers.arcgis.com/javascript/latest/api-reference/esri-support-actions-ActionButton.html) or [ActionToggle](https://developers.arcgis.com/javascript/latest/api-reference/esri-support-actions-ActionToggle.html) class.",
           "docsTags": [
             {
               "name": "see",
@@ -20773,6 +21200,29 @@
           "optional": true,
           "required": false
         },
+        {
+          "name": "closed",
+          "type": "boolean",
+          "complexType": {
+            "original": "boolean",
+            "resolved": "boolean",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "closed",
+          "reflectToAttr": false,
+          "docs": "Indicates whether a component is closed. When `true`, the component will be hidden.",
+          "docsTags": [],
+          "default": "false",
+          "deprecation": "since 4.34, use [`visible`](#visible) instead.",
+          "values": [
+            {
+              "type": "boolean"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
         {
           "name": "collapsed",
           "type": "boolean",
@@ -20875,6 +21325,10 @@
           "reflectToAttr": false,
           "docs": "The number of selected [features](#features) available to the popup.",
           "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            },
             {
               "name": "readonly",
               "text": ""
@@ -20901,7 +21355,12 @@
           "attr": "feature-menu-open",
           "reflectToAttr": false,
           "docs": "This property enables multiple features in the component to display in a list rather than displaying the first selected feature.\nSetting this to `true` allows the user to scroll through the list of features.\nThis value will only be honored if [`initialDisplayMode`](#initialDisplayMode) is set to \"feature\".",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -20944,7 +21403,12 @@
           "attr": "feature-navigation-top",
           "reflectToAttr": false,
           "docs": "Indicates whether the feature navigation arrows are displayed at the top of the component.\nBy default, the navigation arrows are displayed at the bottom of the component.",
-          "docsTags": [],
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "default": "false",
           "values": [
             {
@@ -21011,6 +21475,28 @@
           "optional": true,
           "required": false
         },
+        {
+          "name": "featuresTitle",
+          "type": "string",
+          "complexType": {
+            "original": "string",
+            "resolved": "string",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "features-title",
+          "reflectToAttr": false,
+          "docs": "The title of the Features component.",
+          "docsTags": [],
+          "deprecation": "since 4.34, use [`heading`](#heading) instead.",
+          "values": [
+            {
+              "type": "string"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
         {
           "name": "featureViewModelAbilities",
           "type": "Abilities",
@@ -21351,9 +21837,14 @@
           "mutable": true,
           "attr": "highlight-disabled",
           "reflectToAttr": false,
-          "docs": "Highlight the selected feature using one of the [HighlightOptions](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-support-HighlightOptions.html) defined in the view's\n[highlights](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View.html#highlights) collection.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Features-FeaturesViewModel.html#highlightEnabled)",
-          "docsTags": [],
-          "default": "true",
+          "docs": "Indicates whether to highlight the [selected feature](#selectedFeature) in the associated\n[arcgis-map](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-map/) or [arcgis-scene](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/) component.",
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
+          "default": "false",
           "values": [
             {
               "type": "boolean"
@@ -21389,7 +21880,7 @@
           "required": false
         },
         {
-          "name": "includeDefaultActions",
+          "name": "includeDefaultActionsDisabled",
           "type": "boolean",
           "complexType": {
             "original": "boolean",
@@ -21397,11 +21888,11 @@
             "references": {}
           },
           "mutable": true,
-          "attr": "include-default-actions",
+          "attr": "include-default-actions-disabled",
           "reflectToAttr": false,
-          "docs": "Indicates whether to include the [defaultActions](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Features-FeaturesViewModel.html#includeDefaultActions) in the component.",
+          "docs": "Indicates whether to include the default actions in the component.\nIn order to disable any default actions, it is necessary to set `includeDefaultActionsDisabled` to `true`.",
           "docsTags": [],
-          "default": "true",
+          "default": "false",
           "values": [
             {
               "type": "boolean"
@@ -21669,6 +22160,10 @@
           "reflectToAttr": false,
           "docs": "The feature that the component has drilled into.\nThis feature is either associated with the selected feature in a [relationship](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-RelationshipContent.html) or [utility network](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-UtilityNetworkAssociationsContent.html) element.",
           "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            },
             {
               "name": "readonly",
               "text": ""
@@ -21723,6 +22218,10 @@
           "reflectToAttr": false,
           "docs": "Returns a reference to the current [arcgis-feature](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-feature/) component.\nThis is useful if needing to get a reference to the Feature component in order to make any changes to it.",
           "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            },
             {
               "name": "readonly",
               "text": ""
@@ -21821,7 +22320,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Features-FeaturesViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -21884,8 +22383,13 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\nThe Features component requires a `view` to be set if:\n- The [features](#features) have a popupTemplate containing Arcade expressions in [ExpressionInfo](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-ExpressionInfo.html) or [ExpressionContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-ExpressionContent.html) that may use [geometry functions](https://developers.arcgis.com/arcade/function-reference/geometry_functions/) or reference the `$map` profile variable (i.e. access data from layers within a map). Alternatively, set the [`map`](#map) property.\n- Content is displayed from the popup template of an [aggregate feature](https://developers.arcgis.com/javascript/latest/api-reference/esri-Graphic.html#isAggregate) (i.e. a [cluster](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-support-FeatureReductionCluster.html) or [bin](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-support-FeatureReductionBinning.html)).\n- Values from `date` and `timestamp-offset` fields should respect the view's [time zone](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View.html#timeZone).\nAlternatively, set the [`timeZone`](#timeZone) property.\n- Using the [fetchFeatures](#fetchFeatures) method or the `fetchFeatures` option in the [`open`](#open) method.\n- Using the `Zoom to` default action. If the `view` is not specified, set the [includeDefaultActions](#includeDefaultActions) property to `false` to remove this default action.",
-          "docsTags": [],
+          "docs": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\nThe Features component requires a `view` to be set if:\n- The [features](#features) have a popupTemplate containing Arcade expressions in [ExpressionInfo](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-ExpressionInfo.html) or [ExpressionContent](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-ExpressionContent.html) that may use [geometry functions](https://developers.arcgis.com/arcade/function-reference/geometry_functions/) or reference the `$map` profile variable (i.e. access data from layers within a map). Alternatively, set the [`map`](#map) property.\n- Content is displayed from the popup template of an [aggregate feature](https://developers.arcgis.com/javascript/latest/api-reference/esri-Graphic.html#isAggregate) (i.e. a [cluster](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-support-FeatureReductionCluster.html) or [bin](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-support-FeatureReductionBinning.html)).\n- Values from `date` and `timestamp-offset` fields should respect the view's [time zone](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View.html#timeZone).\nAlternatively, set the [`timeZone`](#timeZone) property.\n- Using the [fetchFeatures](#fetchFeatures) method or the `fetchFeatures` option in the [`open`](#open) method.\n- Using the `Zoom to` default action. If the `view` is not specified, set the [includeDefaultActionsDisabled](#includeDefaultActionsDisabled) property to `true` to remove this default action.",
+          "docsTags": [
+            {
+              "name": "since",
+              "text": "4.34"
+            }
+          ],
           "values": [
             {
               "type": "MapView"
@@ -21931,19 +22435,7 @@
           "attr": "visible",
           "reflectToAttr": false,
           "docs": "Indicates whether the popup is visible. This property is `true` when the popup is querying for results, even if it is not open in the view.\nUse the property to check if the popup is visible and is not",
-          "docsTags": [
-            {
-              "name": "name",
-              "text": "visible"
-            },
-            {
-              "name": "instance"
-            },
-            {
-              "name": "type",
-              "text": "{boolean}"
-            }
-          ],
+          "docsTags": [],
           "default": "false",
           "values": [
             {
@@ -22326,11 +22818,11 @@
         },
         {
           "event": "arcgisPropertyChange",
-          "detail": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedDrillInFeature\" | \"selectedFeature\" | \"selectedFeatureComponent\" | \"selectedFeatureIndex\" | \"visible\"; }",
+          "detail": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"visible\" | \"selectedFeature\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedFeatureIndex\" | \"selectedDrillInFeature\" | \"selectedFeatureComponent\"; }",
           "bubbles": true,
           "complexType": {
-            "original": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedDrillInFeature\" | \"selectedFeature\" | \"selectedFeatureComponent\" | \"selectedFeatureIndex\" | \"visible\"; }",
-            "resolved": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedDrillInFeature\" | \"selectedFeature\" | \"selectedFeatureComponent\" | \"selectedFeatureIndex\" | \"visible\"; }",
+            "original": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"visible\" | \"selectedFeature\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedFeatureIndex\" | \"selectedDrillInFeature\" | \"selectedFeatureComponent\"; }",
+            "resolved": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"visible\" | \"selectedFeature\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedFeatureIndex\" | \"selectedDrillInFeature\" | \"selectedFeatureComponent\"; }",
             "references": {}
           },
           "cancelable": true,
@@ -22493,7 +22985,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon displayed in the widget's button.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -22721,7 +23213,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-FloorFilter.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisFloorFilter component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -24073,7 +24565,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view from which the widget will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-support-GridControls-GridControlsViewModel.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisGridControls component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -24401,7 +24893,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon displayed in the widget's button.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -24762,7 +25254,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The state of the view model.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Slider-SliderViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -25177,7 +25669,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The current state of the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Home-HomeViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -25223,7 +25715,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the widget instance.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Home-HomeViewModel.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisHome component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -25753,7 +26245,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -26250,7 +26742,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-LayerList-LayerListViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -26323,7 +26815,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-LayerList.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLayerList component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "default": "null",
           "values": [
@@ -27183,7 +27675,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Legend-LegendViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -27225,7 +27717,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view from which the widget will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Legend-LegendViewModel.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLegend component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -27622,7 +28114,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLineOfSight component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -29821,22 +30313,22 @@
       ],
       "styles": [
         {
-          "name": "--arcgis-layout-padding-top",
+          "name": "--arcgis-layout-overlay-space-top",
           "annotation": "prop",
           "docs": "Specifies the top padding for the layout."
         },
         {
-          "name": "--arcgis-layout-padding-bottom",
+          "name": "--arcgis-layout-overlay-space-bottom",
           "annotation": "prop",
           "docs": "Specifies the bottom padding for the layout."
         },
         {
-          "name": "--arcgis-layout-padding-left",
+          "name": "--arcgis-layout-overlay-space-left",
           "annotation": "prop",
           "docs": "Specifies the left padding for the layout."
         },
         {
-          "name": "--arcgis-layout-padding-right",
+          "name": "--arcgis-layout-overlay-space-right",
           "annotation": "prop",
           "docs": "Specifies the right padding for the layout."
         }
@@ -30242,7 +30734,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The current state of the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-LinkChartLayoutSwitcher-LinkChartLayoutSwitcherViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -30283,7 +30775,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the widget instance.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-LinkChartLayoutSwitcher-LinkChartLayoutSwitcherViewModel.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLinkChartLayoutSwitcher component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -30579,8 +31071,13 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "",
-          "docsTags": [],
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
+          "docsTags": [
+            {
+              "name": "see",
+              "text": "[Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)"
+            }
+          ],
           "default": "\"gps-off\"",
           "values": [
             {
@@ -30836,7 +31333,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the Module.",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisLocate component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -33386,22 +33883,22 @@
       ],
       "styles": [
         {
-          "name": "--arcgis-layout-padding-top",
+          "name": "--arcgis-layout-overlay-space-top",
           "annotation": "prop",
           "docs": "Specifies the top padding for the layout."
         },
         {
-          "name": "--arcgis-layout-padding-bottom",
+          "name": "--arcgis-layout-overlay-space-bottom",
           "annotation": "prop",
           "docs": "Specifies the bottom padding for the layout."
         },
         {
-          "name": "--arcgis-layout-padding-left",
+          "name": "--arcgis-layout-overlay-space-left",
           "annotation": "prop",
           "docs": "Specifies the left padding for the layout."
         },
         {
-          "name": "--arcgis-layout-padding-right",
+          "name": "--arcgis-layout-overlay-space-right",
           "annotation": "prop",
           "docs": "Specifies the right padding for the layout."
         }
@@ -33670,7 +34167,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -33894,7 +34391,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The ViewModel's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Measurement-MeasurementViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -33944,7 +34441,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Measurement.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisMeasurement component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -34388,7 +34885,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisNavigationToggle component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -34630,7 +35127,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon displayed in the widget's button.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -35022,7 +35519,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-OrientedImageryViewer.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisOrientedImageryViewer component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -35283,7 +35780,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisPlacement component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -35361,60 +35858,23 @@
       "overview": "",
       "readme": "",
       "usage": {},
-      "docs": "<a name=\"overview\"></a>\n\n## Overview\nThe Popup widget allows users to view content from feature attributes. Popups enhance web applications\nby providing users with a simple way to interact with and view attributes in a layer.\nThey play an important role in relaying information to the user, which improves the storytelling capabilities of the application.\n\n<a name=\"loading-the-popup\"></a>\n\n## Loading the Popup\nAt [version 4.27](../release-notes#popup-performance-improvements), the view's default popup is loaded on demand when [`popupEnabled`](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View2D.html#popupEnabled) is set to `true` (which is the default), when the [`openPopup()`](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View2D.html#openPopup) method is called,\nor when some widgets need the popup, such as [Search](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Search.html). Please see the read more section below for details on how to manually load the popup or take\nadvantage of the API lazy loading.\n\n>>> esri-read-more\n\nThe Popup class can be loaded when the [View](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View.html) is instantiated, however, this does not take advantage of the performance improvements of lazily loading the popup.\n```js\n// Create a new MapView\nconst view = new MapView({\n// set the popup property to a new instance of Popup\n  popup: new Popup(...)\n});\n```\nTo utilize the performance improvements and the API automatically lazy loading the popup:\n- Set options/properties on the view's popup:\n  ```js\n  const view = MapView({\n    popup: {\n      dockEnabled: true,\n      dockOptions: {\n        position: true,\n        ...\n      }\n    }\n  });\n  ```\n- Use [`popupEnabled`](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View2D.html#popupEnabled) to prevent the popup appearing when the user clicks the view.\n  ```js\n  // The popup doesn't show for features on selection, but will on Search results and when `openPopup()` is called.\n  view.popupEnabled = false;\n  ```\n- Use [`openPopup()`](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View2D.html#openPopup) instead of [`open()`](#open) and [`closePopup()`](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View2D.html#closePopup) instead of [`close()`](#close).\n  ```js\n  // A deprecation warning is prompted if the popup isn't created\n  // and calls view.openPopup() or view.closePopup() respectively under the hood.\n  view.popup.open(...);\n  view.popup.close(...);\n\n  // Opens or closes the popup on the View.\n  view.openPopup(...);\n  view.closePopup(...);\n  ```\n- Use [reactiveUtils](https://developers.arcgis.com/javascript/latest/api-reference/esri-core-reactiveUtils.html) to watch properties on the popup and its view model instead of the [`watch()`](#watch) method.\n  ```js\n  // This will throw an error that watch() is not a method\n  // since the popup hasn't been created yet.\n  view.popup.watch(\"selectedFeature\", ...)\n\n  // Call reactiveUtils.watch() on popup properties with optional chaining.\n  reactiveUtils.watch(() => view.popup?.selectedFeature, ...);\n  ```\n- Use the [`reactiveUtils.when()`](https://developers.arcgis.com/javascript/latest/api-reference/esri-core-reactiveUtils.html#when) method to check when the popup instance is created. Once its created, then it's properties or methods can be accessed and called.\n  ```js\n  // This will throw an error that actions is not a property.\n  view.popup.actions.push(...);\n\n  // Wait for the popup to load before accessing properties.\n  reactiveUtils.when(() => view.popup?.actions, ()=>{\n    view.popup.actions.push(...);\n  });\n  ```\n\n>>>\n\n<a name=\"popup-ui\"></a>\n\n## Popup UI\nAll [Views](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View.html) contain a default popup.\nThis popup can display generic content, which is set in its [title](#title)\nand [content](#content) properties.\nWhen  content is set directly on the Popup instance it is not tied to a specific feature or layer.\n\n[![popup-basic-example](../assets/img/apiref/widgets/popup/popup-basic.png)](../sample-code/sandbox/?sample=intro-popup)\n\nIn the image above, the text \"Marriage in New York County Census Tract 8\" is the popup's `title`. The remaining text is\nits `content`. A dock button ![popup-dock-btn](../assets/img/apiref/widgets/popup/popup-dock.png) may also be available in the\ntop right corner of the popup. This allows the user to dock the popup to one of the sides or corners of the view.\nThe options for docking may be set in the [dockOptions](#dockOptions) property.\n\nPopups can also contain [actions](#actions) that act like buttons,\nwhich execute a function defined by the developer when clicked.\nBy default, every popup has a \"Zoom to\" action ![popupTemplate-zoom-action](../assets/img/apiref/widgets/popup/popuptemplate-zoom-action.png)\nthat allows users to zoom to the selected feature. See the [actions](#actions)\nproperty for information about adding custom actions to a popup.\n\nThe Popup widget is tied to the [View](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View.html), whether it's docked or anchored to the selected feature.\nIf wanting to utilize the Popup functionality outside of the View, the [Features](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Features.html) widget can be used to display the same content\nin its own container that's not tied to the View.\n\n<a name=\"popup-and-popuptemplate\"></a>\n\n## Popup and PopupTemplate\n[PopupTemplate](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html) is closely related to Popup, but is more specific to [layers](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-Layer.html)\nand [graphics](https://developers.arcgis.com/javascript/latest/api-reference/esri-Graphic.html). It allows you to define custom titles and content templates based on the source of the\n[selected feature](#selectedFeature). When a layer or a graphic has a defined\nPopupTemplate, the popup will display the content\ndefined in the PopupTemplate when the feature is clicked. The content may contain field values from the attributes of the [selected feature](#selectedFeature).\n\nCustom PopupTemplates may also be assigned directly to a popup by setting [graphics](https://developers.arcgis.com/javascript/latest/api-reference/esri-Graphic.html) on the\n[features](#features) property. For more information about Popup\nand how it relates to [PopupTemplate](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html) see the samples listed below.",
+      "docs": "## Overview\nThe Popup component allows users to view content from feature attributes. Popups enhance web applications\nby providing users with a simple way to interact with and view attributes in a layer.\nThey play an important role in relaying information to the user, which improves the storytelling capabilities of the application.\n\n## Popup UI\nThe [arcgis-map](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-map/), [arcgis-scene](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/), or [arcgis-link-chart](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-link-chart/) components contain a default popup.\nThis popup can display generic content, which is set in its [heading](#heading)\nand [content](#content) properties.\nWhen  content is set directly on the Popup instance it is not tied to a specific feature or layer.\n\n[![popup-basic-example](https://developers.arcgis.com/javascript/latest/assets/img/apiref/widgets/popup/popup-basic.png)](../sample-code/sandbox/?sample=intro-popup)\n\nIn the image above, the text \"Marriage in Nassau County Census Tract 5177.01\" is the popup's [heading](#heading).\nThe remaining text is the popup's [`content`](#content).\nA dock button is displayed in the top right corner of the popup allowing the user to dock the popup to one of the sides or corners of the view.\nThe options for docking may be set in the [dockOptions](#dockOptions) property.\nThe popup may also be collapsed by clicking the collapse button (the down arrow icon) in the top right corner of the popup.\nWhen collapsed, only the heading of the popup displays.\nThe popup may be closed by clicking the close button (the \"x\" icon) in the top right corner of the popup.\n\nPopups can also contain [actions](#actions) which execute a function defined by the developer when clicked.\nBy default, every popup has a \"Zoom to\" action (as shown in the image above with the magnifying glass) that allows users to zoom to the selected feature.\nSee the [actions](#actions) property for information about adding custom actions to a popup.\n\nThe Popup component is tied to a [arcgis-map](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-map/), [arcgis-scene](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/), or [arcgis-link-chart](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-link-chart/) component, whether it's docked or anchored to the selected feature.\nIf wanting to utilize the Popup functionality outside of [arcgis-map](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-map/), [arcgis-scene](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/), or [arcgis-link-chart](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-link-chart/), the [arcgis-features](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-features/) component can be used to display the same content\nin its own container.\n\n## Popup and PopupTemplate\n[PopupTemplates](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html) are closely related to Popup, but are more specific to [layers](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-Layer.html)\nand [graphics](https://developers.arcgis.com/javascript/latest/api-reference/esri-Graphic.html). Popup templates allow you to define custom titles and content templates based on the source of the\n[selected feature](#selectedFeature). When a layer or a graphic has a defined\npopup template, the popup will display the content defined in the popup template when the feature is clicked.\nThe content may contain field values from the attributes of the [selected feature](#selectedFeature).\n\nCustom PopupTemplates may also be assigned directly to a popup by setting [graphics](https://developers.arcgis.com/javascript/latest/api-reference/esri-Graphic.html) on the\n[features](#features) property.",
       "docsTags": [
         {
           "name": "since",
-          "text": "4.0"
-        },
-        {
-          "name": "see",
-          "text": "module :esri/PopupTemplate"
-        },
-        {
-          "name": "see",
-          "text": "module :esri/views/SceneView#popup"
-        },
-        {
-          "name": "see",
-          "text": "module :esri/views/View2D#popup"
-        },
-        {
-          "name": "see",
-          "text": "[Sample - Intro to popups](../sample-code/intro-popup/index.html)"
-        },
-        {
-          "name": "see",
-          "text": "[Sample - to PopupTemplate](../sample-code/intro-popuptemplate/index.html)"
-        },
-        {
-          "name": "see",
-          "text": "[Sample - Dock positions with popup](../sample-code/popup-docking-position/index.html)"
-        },
-        {
-          "name": "see",
-          "text": "[Sample - Popup actions](../sample-code/popup-actions/index.html)"
+          "text": "4.34"
         },
         {
-          "name": "see",
-          "text": "[Sample - Custom popup actions per feature](../sample-code/popup-custom-action/index.html)"
+          "name": "beta"
         },
         {
           "name": "see",
-          "text": "[Sample - Popup with edit action](../sample-code/popup-editaction/index.html)"
-        },
-        {
-          "name": "see",
-          "text": "[Sample - Popup with DOM node](../sample-code/popup-domnode/index.html)"
+          "text": "module :esri/PopupTemplate"
         },
         {
           "name": "see",
           "text": "[Guide - Esri Icon Font](../guide/esri-icon-font/index.html)"
         },
-        {
-          "name": "see",
-          "text": "module :esri/widgets/Popup/PopupViewModel"
-        },
         {
           "name": "superclass",
           "text": "{\"name\":\"LitElement\",\"package\":\"@arcgis/lumina\"}"
@@ -35451,7 +35911,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "[Collection](https://developers.arcgis.com/javascript/latest/api-reference/esri-core-Collection.html) of [action](https://developers.arcgis.com/javascript/latest/api-reference/esri-support-actions-ActionButton.html) or [action](https://developers.arcgis.com/javascript/latest/api-reference/esri-support-actions-ActionToggle.html) objects.\nEach action may be executed by clicking the icon or image symbolizing them.\nBy default, popups have a `Zoom To` action styled with a magnifying glass icon ![popupTemplate-zoom-action](../assets/img/apiref/widgets/popup/popuptemplate-zoom-action.png).\nWhen this icon is clicked, the view zooms in four LODs and centers on the selected feature.\n\nYou may remove this default action by setting [includeDefaultActions](#includeDefaultActions) to `false`, or by setting the\n[`overwriteActions`](esri-PopupTemplate.html#overwriteActions) property to `true` in a [PopupTemplate](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html).\nThe order of each action is the order in which they appear in the actions [Collection](https://developers.arcgis.com/javascript/latest/api-reference/esri-core-Collection.html).\n\nThe [trigger-action](#event-trigger-action) event fires each time an action is clicked.\n\nActions are defined with the properties listed in the [ActionButton](https://developers.arcgis.com/javascript/latest/api-reference/esri-support-actions-ActionButton.html) or [ActionToggle](https://developers.arcgis.com/javascript/latest/api-reference/esri-support-actions-ActionToggle.html) classes.",
+          "docs": "A [collection](https://developers.arcgis.com/javascript/latest/api-reference/esri-core-Collection.html) of [action button](https://developers.arcgis.com/javascript/latest/api-reference/esri-support-actions-ActionButton.html) or [action toggle](https://developers.arcgis.com/javascript/latest/api-reference/esri-support-actions-ActionToggle.html) objects.\nEach action may be executed by clicking the icon or image symbolizing them.\n\nBy default, popups have a `Zoom To` action styled with a magnifying glass icon.\nWhen this icon is clicked, the view zooms in four LODs and centers on the selected feature.\nYou may remove this default action by setting [includeDefaultActionsDisabled](#includeDefaultActionsDisabled) to `true`, or by setting the\n[`overwriteActions`](esri-PopupTemplate.html#overwriteActions) property to `true` in a [PopupTemplate](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html).\n\nThe order of each action is the order in which they appear in the actions [Collection](https://developers.arcgis.com/javascript/latest/api-reference/esri-core-Collection.html).\n\nThe [arcgisTriggerAction](#arcgisTriggerAction) event fires each time an action is clicked.",
           "docsTags": [
             {
               "name": "autocast",
@@ -35459,7 +35919,7 @@
             },
             {
               "name": "see",
-              "text": "[trigger-action](#event-trigger-action)"
+              "text": "[arcgisTriggerAction](#arcgisTriggerAction)"
             },
             {
               "name": "see",
@@ -35475,7 +35935,7 @@
             },
             {
               "name": "example",
-              "text": "// Defines an action button to zoom out from the selected feature\nconst zoomOutAction = {\n  type: \"button\",\n  // This text is displayed as a tooltip\n  title: \"Zoom out\",\n  // The ID by which to reference the action in the event handler\n  id: \"zoom-out\",\n  // Sets the icon used to style the action button\n  icon: \"magnifying-glass-minus\"\n};\n// Adds the custom action to the popup.\nview.popup.actions.push(zoomOutAction);"
+              "text": "```js\n// Defines an action button to zoom out from the selected feature\nconst zoomOutAction = {\n  type: \"button\",\n  // This text is displayed as a tooltip\n  title: \"Zoom out\",\n  // The ID by which to reference the action in the event handler\n  id: \"zoom-out\",\n  // Sets the icon used to style the action button\n  icon: \"magnifying-glass-minus\"\n};\n// Adds the custom action to the popup.\npopupComponent.actions.push(zoomOutAction);\n```"
             }
           ],
           "values": [],
@@ -35492,12 +35952,8 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "Indicates if the widget is active when it is visible and is not [waiting](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Popup-PopupViewModel.html#waitingForResult).",
+          "docs": "Indicates if the component is active when it is visible and is not [waiting](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Popup-PopupViewModel.html#waitingForResult).",
           "docsTags": [
-            {
-              "name": "since",
-              "text": "4.30"
-            },
             {
               "name": "readonly",
               "text": ""
@@ -35531,13 +35987,9 @@
           "reflectToAttr": false,
           "docs": "Position of the popup in relation to the selected feature. The default behavior\nis to display above the feature and adjust if not enough room. If needing\nto explicitly control where the popup displays in relation to the feature, choose\nan option besides `auto`.",
           "docsTags": [
-            {
-              "name": "since",
-              "text": "4.8"
-            },
             {
               "name": "example",
-              "text": "// Popup will display on the bottom-right of the selected feature regardless of where that feature is located\nview.popup.alignment = \"bottom-right\";"
+              "text": "```js\n// Popup will display on the bottom-right of the selected feature regardless of where that feature is located\npopupComponent.alignment = \"bottom-right\";\n```"
             }
           ],
           "default": "\"auto\"",
@@ -35605,12 +36057,7 @@
           "attr": "auto-close-enabled",
           "reflectToAttr": false,
           "docs": "This closes the popup when the [View](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View.html) camera or [Viewpoint](https://developers.arcgis.com/javascript/latest/api-reference/esri-Viewpoint.html) changes.",
-          "docsTags": [
-            {
-              "name": "since",
-              "text": "4.5"
-            }
-          ],
+          "docsTags": [],
           "default": "false",
           "values": [
             {
@@ -35654,10 +36101,6 @@
           "reflectToAttr": false,
           "docs": "Indicates whether the popup displays its content. If `true`, only the header displays.",
           "docsTags": [
-            {
-              "name": "since",
-              "text": "4.5"
-            },
             {
               "name": "readonly",
               "text": ""
@@ -35709,7 +36152,7 @@
             },
             {
               "name": "example",
-              "text": "// This sets generic instructions in the popup that will always be displayed\n// unless it is overridden by a PopupTemplate\nview.popup.content = \"Click a feature on the map to view its attributes\";"
+              "text": "```js\n// This sets generic instructions in the popup that will always be displayed\n// unless it is overridden by a PopupTemplate\npopupComponent.content = \"Click a feature on the map to view its attributes\";\n```"
             }
           ],
           "values": [
@@ -35736,7 +36179,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "Dock position in the [View](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View.html).",
+          "docs": "Dock position in the [arcgis-map](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-map/), [arcgis-scene](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/), or [arcgis-link-chart](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-link-chart/) component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -35783,13 +36226,8 @@
           "mutable": true,
           "attr": "default-popup-template-enabled",
           "reflectToAttr": false,
-          "docs": "Enables automatic creation of a popup template for layers that have popups enabled but no\npopupTemplate defined. Automatic popup templates are supported for layers that\nsupport the `createPopupTemplate` method. (Supported for\n[FeatureLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-FeatureLayer.html),\n[GeoJSONLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-GeoJSONLayer.html),\n[OGCFeatureLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-OGCFeatureLayer.html),\n[SceneLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-SceneLayer.html),\n[CSVLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-CSVLayer.html),\n[PointCloudLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-PointCloudLayer.html),\n[StreamLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-StreamLayer.html),\n[ImageryLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-ImageryLayer.html), and\n[VoxelLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-VoxelLayer.html)).\n\n::: esri-md class=\"warning\"\n* Starting with version 4.12, [PopupTemplate](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html) content can no longer be set using a\nwildcard, e.g. `*`. Instead, set the `defaultPopupTemplateEnabled` property to `true`.\n* Starting with 4.16, the default popup has been improved to no longer display system\n[fields](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-FieldInfo.html)\nthat do not hold significant value, e.g. `Shape__Area` and `Shape__Length` are two fields that\nno longer display.\n* Starting with version 4.28, `date` fields are formatted using the `short-date-short-time` preset [dateFormat](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-support-FieldInfoFormat.html#dateFormat)\nrather than `long-month-day-year` in default [popup](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html) created by setting the `defaultPopupTemplateEnabled` property to `true`.\nFor example, previously a date that may have appeared as `\"December 30, 1997\"` will now appear as `\"12/30/1997 6:00 PM\"`.\n:::",
-          "docsTags": [
-            {
-              "name": "since",
-              "text": "4.11"
-            }
-          ],
+          "docs": "Enables automatic creation of a popup template for layers that have popups enabled but no\npopupTemplate defined. Automatic popup templates are supported for layers that\nsupport the `createPopupTemplate` method. (Supported for\n[FeatureLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-FeatureLayer.html),\n[GeoJSONLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-GeoJSONLayer.html),\n[OGCFeatureLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-OGCFeatureLayer.html),\n[SceneLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-SceneLayer.html),\n[CSVLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-CSVLayer.html),\n[PointCloudLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-PointCloudLayer.html),\n[StreamLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-StreamLayer.html),\n[ImageryLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-ImageryLayer.html), and\n[VoxelLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-VoxelLayer.html)).\n\n**Note:**\n* Starting with version 4.12, [PopupTemplate](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html) content can no longer be set using a\nwildcard, e.g. `*`. Instead, set the `defaultPopupTemplateEnabled` property to `true`.\n* Starting with 4.16, the default popup has been improved to no longer display system\n[fields](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-FieldInfo.html)\nthat do not hold significant value, e.g. `Shape__Area` and `Shape__Length` are two fields that\nno longer display.\n* Starting with version 4.28, `date` fields are formatted using the `short-date-short-time` preset [dateFormat](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-support-FieldInfoFormat.html#dateFormat)\nrather than `long-month-day-year` in default [popup](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html) created by setting the `defaultPopupTemplateEnabled` property to `true`.\nFor example, previously a date that may have appeared as `\"December 30, 1997\"` will now appear as `\"12/30/1997 6:00 PM\"`.",
+          "docsTags": [],
           "default": "false",
           "values": [
             {
@@ -35818,7 +36256,11 @@
             },
             {
               "name": "example",
-              "text": "// The popup will automatically be dockEnabled when made visible\nview.popup.dockEnabled = true;"
+              "text": "```html\n<!-- Setting this property in HTML -->\n<arcgis-popup dock-enabled></arcgis-popup>\n```"
+            },
+            {
+              "name": "example",
+              "text": "```js\n// Setting this property using JS.\n// The popup will automatically be dockEnabled when made visible\npopupComponent.dockEnabled = true;\n```"
             }
           ],
           "default": "false",
@@ -35854,7 +36296,7 @@
             },
             {
               "name": "example",
-              "text": "view.popup.dockOptions = {\n  // Disable the dock button so users cannot undock the popup\n  buttonEnabled: false,\n  // Dock the popup when the size of the view is less than or equal to 600x1000 pixels\n  breakpoint: {\n    width: 600,\n    height: 1000\n  }\n};"
+              "text": "```js\npopupComponent.dockOptions = {\n  // Disable the dock button so users cannot undock the popup\n  buttonEnabled: false,\n  // Dock the popup when the size of the view is less than or equal to 600x1000 pixels\n  breakpoint: {\n    width: 600,\n    height: 1000\n  }\n};\n```"
             }
           ],
           "values": [],
@@ -35898,7 +36340,7 @@
           "mutable": true,
           "attr": "feature-menu-open",
           "reflectToAttr": false,
-          "docs": "This property enables showing the list of features.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Features-FeaturesViewModel.html#featureMenuOpen)",
+          "docs": "This property enables showing a list of features.\nSetting this to `true` allows the user to scroll through the list of features.\nThis value will only be honored if [`initialDisplayMode`](#initialDisplayMode) is set to \"feature\".",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -35937,7 +36379,7 @@
             },
             {
               "name": "example",
-              "text": "// When setting the features property, the graphics pushed to this property\n// must have a PopupTemplate set.\nlet g1 = new Graphic();\ng1.popupTemplate = new PopupTemplate({\n  title: \"Results title\",\n  content: \"Results: {ATTRIBUTE_NAME}\"\n});\n// Set the graphics as an array to the popup instance. The content and title of\n// the popup will be set depending on the PopupTemplate of the graphics.\n// Each graphic may share the same PopupTemplate or have a unique PopupTemplate\nlet graphics = [g1, g2, g3, g4, g5];\nview.popup.features = graphics;"
+              "text": "```js\n// When setting the features property, the graphics pushed to this property\n// must have a PopupTemplate set.\nlet g1 = new Graphic();\ng1.popupTemplate = new PopupTemplate({\n  title: \"Results title\",\n  content: \"Results: {ATTRIBUTE_NAME}\"\n});\n// Set the graphics as an array to the popup instance. The content and title of\n// the popup will be set depending on the PopupTemplate of the graphics.\n// Each graphic may share the same PopupTemplate or have a unique PopupTemplate\nlet graphics = [g1, g2, g3, g4, g5];\npopupComponent.features = graphics;\n```"
             }
           ],
           "values": [],
@@ -35954,8 +36396,13 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "This function provides the ability to override either the\n[MapView goTo()](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#goTo) or\n[SceneView goTo()](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html#goTo) methods.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Features-FeaturesViewModel.html#goToOverride)",
-          "docsTags": [],
+          "docs": "This function provides the ability to override either the [arcgis-map.goTo](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-map/#goTo) or [arcgis-scene.goTo](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/#goTo) methods.",
+          "docsTags": [
+            {
+              "name": "example",
+              "text": "```js\npopupComponent.goToOverride = (viewElement, goToParams)=>  {\n  goToParams.options = {\n    speedFactor: 2\n  };\n  return viewElement.goTo(goToParams.target, goToParams.options);\n};\n```"
+            }
+          ],
           "values": [],
           "optional": true,
           "required": false
@@ -35979,7 +36426,11 @@
             },
             {
               "name": "example",
-              "text": "// This title will display in the popup unless a selected feature's\n// PopupTemplate overrides it\nview.popup.title = \"Population by zip codes in Southern California\";"
+              "text": "```html\n<!-- This title will display in the popup unless a selected feature's\n    PopupTemplate overrides it -->\n<arcgis-popup heading=\"Population by zip codes in Southern California\"></arcgis-popup>\n```"
+            },
+            {
+              "name": "example",
+              "text": "```js\n// This title will display in the popup unless a selected feature's\n// PopupTemplate overrides it\npopupComponent.title = \"Population by zip codes in Southern California\";\n```"
             }
           ],
           "values": [
@@ -36001,19 +36452,19 @@
           "mutable": true,
           "attr": "heading-level",
           "reflectToAttr": false,
-          "docs": "Indicates the heading level to use for the [title](#title) of the popup.\nBy default, the title is rendered\nas a level 2 heading (e.g. `<h2>Popup title</h2>`). Depending on the widget's placement\nin your app, you may need to adjust this heading for proper semantics. This is\nimportant for meeting accessibility standards.",
+          "docs": "Indicates the heading level to use for the [heading](#heading) of the popup.\nBy default, the heading is rendered\nas a level 2 heading (e.g. `<h2>Popup title</h2>`). Depending on the component's placement\nin your app, you may need to adjust this heading for proper semantics. This is\nimportant for meeting accessibility standards.",
           "docsTags": [
             {
-              "name": "since",
-              "text": "4.20"
+              "name": "see",
+              "text": "[Heading Elements](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Heading_Elements)"
             },
             {
               "name": "see",
-              "text": "[Heading Elements](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/Heading_Elements)"
+              "text": "[heading](#heading)"
             },
             {
               "name": "example",
-              "text": "// popup title will render as an <h3>\npopup.headingLevel = 3;"
+              "text": "```html\n<!-- Render the popup heading as a level 3 heading -->\n<arcgis-popup heading=\"Popup title\" heading-level=\"3\"></arcgis-popup>\n```"
             }
           ],
           "default": "2",
@@ -36057,7 +36508,7 @@
           "mutable": true,
           "attr": "hide-action-bar",
           "reflectToAttr": false,
-          "docs": "This property provides the ability to turn individual elements of the component's display on/off.",
+          "docs": "Indicates whether to hide the action bar that holds the feature's [actions](#actions).",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -36079,7 +36530,7 @@
           "mutable": true,
           "attr": "hide-close-button",
           "reflectToAttr": false,
-          "docs": "This property provides the ability to turn individual elements of the component's display on/off.",
+          "docs": "Indicates whether to hide the close button in the component.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -36101,7 +36552,7 @@
           "mutable": true,
           "attr": "hide-collapse-button",
           "reflectToAttr": false,
-          "docs": "This property provides the ability to turn individual elements of the component's display on/off.",
+          "docs": "Indicates whether to hide the collapse button in the component.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -36123,7 +36574,7 @@
           "mutable": true,
           "attr": "hide-feature-list-layer-title",
           "reflectToAttr": false,
-          "docs": "This property provides the ability to turn individual elements of the component's display on/off.",
+          "docs": "Indicates whether to hide the group heading for a list of multiple features in the feature menu.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -36145,7 +36596,7 @@
           "mutable": true,
           "attr": "hide-feature-menu-heading",
           "reflectToAttr": false,
-          "docs": "This property provides the ability to turn individual elements of the component's display on/off.",
+          "docs": "Indicates whether to hide a heading and description on the component feature menu list.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -36167,7 +36618,7 @@
           "mutable": true,
           "attr": "hide-feature-navigation",
           "reflectToAttr": false,
-          "docs": "This property provides the ability to turn individual elements of the component's display on/off.",
+          "docs": "Indicates whether pagination for feature navigation will be displayed. This allows the user to scroll through various [selected features](#features) using pagination arrows.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -36189,7 +36640,7 @@
           "mutable": true,
           "attr": "hide-heading",
           "reflectToAttr": false,
-          "docs": "This property provides the ability to turn individual elements of the component's display on/off.",
+          "docs": "Indicates whether to hide the heading in the component.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -36211,7 +36662,7 @@
           "mutable": true,
           "attr": "hide-spinner",
           "reflectToAttr": false,
-          "docs": "This property provides the ability to turn individual elements of the component's display on/off.",
+          "docs": "Indicates whether to hide the spinner in the component.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -36233,7 +36684,29 @@
           "mutable": true,
           "attr": "highlight-disabled",
           "reflectToAttr": false,
-          "docs": "Highlight the selected popup feature using the [highlights](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#highlights)\nset on the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or the [highlights](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html#highlights)\nset on the [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).",
+          "docs": "Indicates if the selected feature will be highlighted.\nThis is done using the [arcgis-map.highlights](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-map/#highlights) or the [arcgis-scene.highlights](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/#highlights).",
+          "docsTags": [],
+          "default": "false",
+          "values": [
+            {
+              "type": "boolean"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
+        {
+          "name": "includeDefaultActionsDisabled",
+          "type": "boolean",
+          "complexType": {
+            "original": "boolean",
+            "resolved": "boolean",
+            "references": {}
+          },
+          "mutable": true,
+          "attr": "include-default-actions-disabled",
+          "reflectToAttr": false,
+          "docs": "Indicates whether to include the default actions in the component.\nIn order to disable any default actions, it is necessary to set `includeDefaultActionsDisabled` to `true`.",
           "docsTags": [],
           "default": "false",
           "values": [
@@ -36256,12 +36729,7 @@
           "attr": "initial-display-mode",
           "reflectToAttr": false,
           "docs": "Indicates whether to initially display a list of features, or the content for one feature.",
-          "docsTags": [
-            {
-              "name": "since",
-              "text": "4.32"
-            }
-          ],
+          "docsTags": [],
           "default": "\"feature\"",
           "values": [
             {
@@ -36287,7 +36755,7 @@
           "mutable": true,
           "attr": "label",
           "reflectToAttr": false,
-          "docs": "The widget's default label.",
+          "docs": "The component's default label.",
           "docsTags": [],
           "values": [
             {
@@ -36325,15 +36793,15 @@
             },
             {
               "name": "example",
-              "text": "// Sets the location of the popup to the center of the view\nview.popup.location = view.center;\n// Displays the popup\nview.popup.visible = true;"
+              "text": "```js\n// Sets the location of the popup to the center of the view\npopupComponent.location = viewELement.center;\n// Displays the popup\npopupComponent.visible = true;\n```"
             },
             {
               "name": "example",
-              "text": "// Sets the location of the popup to a specific place (using autocast)\n// Note: using latitude/longitude only works if view is in Web Mercator or WGS84 spatial reference.\nview.popup.location = {latitude: 34.0571, longitude: -117.1968};"
+              "text": "```js\n// Sets the location of the popup to a specific place (using autocast)\n// Note: using latitude/longitude only works if view is in Web Mercator or WGS84 spatial reference.\npopupComponent.location = {latitude: 34.0571, longitude: -117.1968};\n```"
             },
             {
               "name": "example",
-              "text": "// Sets the location of the popup to the location of a click on the view\nreactiveUtils.on(()=>view, \"click\", (event)=>{\n  view.popup.location = event.mapPoint;\n  // Displays the popup\n  view.popup.visible = true;\n});"
+              "text": "```js\n// Sets the location of the popup to the location of a click on the view\nreactiveUtils.on(()=>viewElement, \"arcgisViewClick\", (event)=>{\n  popupComponent.location = event.detail.mapPoint;\n  // Displays the popup\n  popupComponent.visible = true;\n});\n```"
             }
           ],
           "values": [],
@@ -36415,8 +36883,13 @@
           "mutable": true,
           "attr": "reference-element",
           "reflectToAttr": false,
-          "docs": "",
-          "docsTags": [],
+          "docs": "By assigning the `id` attribute of the Map or Scene component to this property, you can position a child component anywhere in the DOM while still maintaining a connection to the Map or Scene.",
+          "docsTags": [
+            {
+              "name": "see",
+              "text": "[Associate components with a Map or Scene component](https://developers.arcgis.com/javascript/latest/programming-patterns/#associate-components-with-a-map-or-scene-component)"
+            }
+          ],
           "values": [
             {
               "type": "HTMLArcgisLinkChartElement"
@@ -36450,12 +36923,8 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The feature that the widget has drilled into.\nThis feature is either associated with the selected feature in a [relationship](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-RelationshipContent.html) or [utility](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-UtilityNetworkAssociationsContent.html).",
+          "docs": "The feature that the component has drilled into.\nThis feature is either associated with the selected feature in a [relationship](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-RelationshipContent.html) or [utility network](https://developers.arcgis.com/javascript/latest/api-reference/esri-popup-content-UtilityNetworkAssociationsContent.html) element.",
           "docsTags": [
-            {
-              "name": "since",
-              "text": "4.32"
-            },
             {
               "name": "readonly",
               "text": ""
@@ -36508,12 +36977,8 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "Returns a reference to the current [Feature](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Feature.html) that the Popup is using.\nThis is useful if needing to get a reference to the widget in order to make any changes to it.",
+          "docs": "Returns a reference to the current [arcgis-feature](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-feature/) that the Popup is using.\nThis is useful if needing to get a reference to the component in order to make any changes to it.",
           "docsTags": [
-            {
-              "name": "since",
-              "text": "4.7"
-            },
             {
               "name": "readonly",
               "text": ""
@@ -36555,7 +37020,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Features-FeaturesViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -36587,15 +37052,12 @@
           "mutable": true,
           "attr": "visible",
           "reflectToAttr": false,
-          "docs": "Indicates whether the popup is visible. This property is `true` when the popup is querying for results, even if it is not open in the view.\nUse the property to check if the popup is visible and is not",
+          "docs": "Indicates whether the popup is visible. This property is `true` when the popup is querying for results, even if it is not open.\nUse the property to check if the popup is visible and is not.",
           "docsTags": [
             {
               "name": "name",
               "text": "visible"
             },
-            {
-              "name": "instance"
-            },
             {
               "name": "type",
               "text": "{boolean}"
@@ -36632,7 +37094,7 @@
           },
           "signature": "clear(): Promise<void>",
           "parameters": [],
-          "docs": "Removes [promises](#promises), [features](#features), [content](#content),\n[title](#title) and [location](#location) from the Popup.",
+          "docs": "Removes all [promises](#promises), [features](#features), [content](#content),\n[heading](#heading) and [location](#location) from the Popup.",
           "docsTags": []
         },
         {
@@ -36747,19 +37209,11 @@
               "docs": ""
             }
           ],
-          "docs": "Use this method to return feature(s) at a given screen location.\nThese features are fetched from all of the [LayerViews](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-layers-LayerView.html)\nin the [view](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View.html). In order to use this, a layer must already have an\nassociated [PopupTemplate](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html) and have its [popupEnabled](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-FeatureLayer.html#popupEnabled).\nThese features can then be used within a custom [Popup](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Popup.html)\nor [Feature](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Feature.html) widget experience.\nOne example could be a custom side panel that displays feature-specific information based on\nan end user's click location. This method allows a developer the ability to\ncontrol how the input location is handled, and then subsequently, what to do with the results.",
+          "docs": "Use this method to return feature(s) at a given screen location.\nThese features are fetched from all of the [LayerViews](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-layers-LayerView.html)\nin the [view](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View.html). In order to use this, a layer must already have an\nassociated [PopupTemplate](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html) and have its [popupEnabled](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-FeatureLayer.html#popupEnabled).",
           "docsTags": [
             {
               "name": "example",
-              "text": "// Add Feature widget to UI\nview.ui.add(featureWidget, \"top-right\");\n\n// Get view's click event\nreactiveUtils.on(()=>view, \"click\", (event)=>{\n  // Call fetchFeatures and pass in the click event screenPoint\n  view.popup.fetchFeatures(event.screenPoint).then((response) => {\n    // Access the response from fetchFeatures\n    response.allGraphicsPromise.then((graphics) => {\n      // Set the feature widget's graphic to the returned graphic from fetchFeatures\n      featureWidget.graphic = graphics[0];\n    });\n  });\n});"
-            },
-            {
-              "name": "since",
-              "text": "4.15"
-            },
-            {
-              "name": "see",
-              "text": "[Sample - Feature widget - Query graphics from multiple layers](../sample-code/widgets-feature-multiplelayers/index.html)"
+              "text": "```js\n// Example showing how to use fetchFeatures in an application\n// with the popup and feature components.\nconst popupComponent = document.querySelector(\"arcgis-popup\");\nconst viewElement = document.querySelector(\"arcgis-map\");\nconst featureComponent = document.querySelector(\"arcgis-feature\");\n// Get viewElement's click event\nreactiveUtils.on(()=>viewElement, \"arcgisViewClick\", (event)=>{\n  const { screenPoint } = event.detail;\n  // Call fetchFeatures on the popup and pass in the click event screenPoint\n  popupComponent.fetchFeatures(screenPoint).then((response) => {\n    // Access the response from fetchFeatures\n    response.allGraphicsPromise.then((graphics) => {\n      // Set the feature component's graphic to the returned graphic from fetchFeatures\n      featureComponent.graphic = graphics[0];\n    });\n  });\n});\n```"
             }
           ]
         },
@@ -36833,39 +37287,27 @@
               "docs": ""
             }
           ],
-          "docs": "Opens the popup at the given location with content defined either explicitly with `content`\nor driven from the [PopupTemplate](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html) of input features. This method sets\nthe popup's [visible](#visible) property to `true`. Users can alternatively open the popup\nby directly setting the [visible](#visible) property to `true`.\n\n::: esri-md class=\"warning\"\nThe popup will only display if\nthe view's size constraints in [dockOptions](#dockOptions) are met or the [location](#location)\nproperty is set to a geometry.\n:::",
+          "docs": "Opens the popup at the given location with content defined either explicitly with `content`\nor driven from the [PopupTemplate](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html) of input features. This method sets\nthe popup's [visible](#visible) property to `true`. Users can alternatively open the popup\nby directly setting the [visible](#visible) property to `true`.\n\n***Note:***\nThe popup will only display if the [arcgis-map](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-map/) or [arcgis-scene](https://developers.arcgis.com/javascript/latest/references/map-components/arcgis-scene/) size constraints in [dockOptions](#dockOptions) are met or the [location](#location)\nproperty is set to a geometry.",
           "docsTags": [
             {
               "name": "see",
-              "text": "[Intro to popups](../sample-code/intro-popup/index.html)"
-            },
-            {
-              "name": "see",
-              "text": "[Popup.visible](#visible)"
-            },
-            {
-              "name": "see",
-              "text": "[Sample - Query with `rest/query`](../sample-code/query/index.html)"
-            },
-            {
-              "name": "see",
-              "text": "[Sample - Popup with DOM node](../sample-code/popup-domnode/index.html)"
+              "text": "[visible](#visible)"
             },
             {
               "name": "example",
-              "text": "reactiveUtils.on(()=>view, \"click\", (event)=>{\n  view.popup.open({\n   location: event.mapPoint,  // location of the click on the view\n   title: \"You clicked here\",  // title displayed in the popup\n   content: \"This is a point of interest\"  // content displayed in the popup\n  });\n});"
+              "text": "```js\nreactiveUtils.on(()=>viewElement, \"arcgisViewClick\", (event)=>{\n const { mapPoint } = event.detail;\n  popupComponent.open({\n   location: mapPoint,  // location of the click on the view\n   title: \"You clicked here\",  // title displayed in the popup\n   content: \"This is a point of interest\"  // content displayed in the popup\n  });\n});\n```"
             },
             {
               "name": "example",
-              "text": "reactiveUtils.on(()=>view, \"click\", (event)=>{\n   view.popup.open({\n     location: event.mapPoint,  // location of the click on the view\n     fetchFeatures: true // display the content for the selected feature if a popupTemplate is defined.\n   });\n });"
+              "text": "```js\nreactiveUtils.on(()=>viewElement, \"arcgisViewClick\", (event)=>{\n   const { mapPoint } = event.detail;\n   popupComponent.open({\n     location: mapPoint,  // location of the click on the view\n     fetchFeatures: true // display the content for the selected feature if a popupTemplate is defined.\n   });\n });\n```"
             },
             {
               "name": "example",
-              "text": "view.popup.open({\n  title: \"You clicked here\",  // title displayed in the popup\n  content: \"This is a point of interest\",  // content displayed in the popup\n  location: event.mapPoint,\n  updateLocationEnabled: true  // updates the location of popup based on\n  // selected feature's geometry\n});"
+              "text": "```js\npopupComponent.open({\n  title: \"You clicked here\",  // title displayed in the popup\n  content: \"This is a point of interest\",  // content displayed in the popup\n  location: event.detail.mapPoint,\n  updateLocationEnabled: true  // updates the location of popup based on\n  // selected feature's geometry\n});\n```"
             },
             {
               "name": "example",
-              "text": "view.popup.open({\n  features: graphics,  // array of graphics\n  featureMenuOpen: true, // selected features initially display in a list\n  location: graphics[0].geometry // location of the first graphic in the array of graphics\n});"
+              "text": "```js\npopupComponent.open({\n  features: graphics,  // array of graphics\n  featureMenuOpen: true, // selected features initially display in a list\n  location: graphics[0].geometry // location of the first graphic in the array of graphics\n});\n```"
             }
           ]
         },
@@ -36923,12 +37365,7 @@
           "signature": "setFocus(): Promise<void>",
           "parameters": [],
           "docs": "Use this method to give focus to the Widget if the widget is able to be focused.",
-          "docsTags": [
-            {
-              "name": "since",
-              "text": "4.6"
-            }
-          ]
+          "docsTags": []
         },
         {
           "name": "triggerAction",
@@ -36972,7 +37409,7 @@
               "docs": ""
             }
           ],
-          "docs": "Triggers the [trigger-action](#event-trigger-action) event and executes the [action](#actions)\nat the specified index in the [actions](#actions) array.",
+          "docs": "Triggers the [arcgisTriggerAction](#arcgisTriggerAction) event and executes the [action](#actions)\nat the specified index in the [actions](#actions) array.",
           "docsTags": []
         }
       ],
@@ -36993,11 +37430,11 @@
         },
         {
           "event": "arcgisPropertyChange",
-          "detail": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedDrillInFeature\" | \"selectedFeature\" | \"selectedFeatureComponent\" | \"selectedFeatureIndex\" | \"visible\" | \"currentAlignment\" | \"dockEnabled\"; }",
+          "detail": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"visible\" | \"selectedFeature\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedFeatureIndex\" | \"selectedDrillInFeature\" | \"selectedFeatureComponent\" | \"currentAlignment\" | \"dockEnabled\"; }",
           "bubbles": true,
           "complexType": {
-            "original": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedDrillInFeature\" | \"selectedFeature\" | \"selectedFeatureComponent\" | \"selectedFeatureIndex\" | \"visible\" | \"currentAlignment\" | \"dockEnabled\"; }",
-            "resolved": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedDrillInFeature\" | \"selectedFeature\" | \"selectedFeatureComponent\" | \"selectedFeatureIndex\" | \"visible\" | \"currentAlignment\" | \"dockEnabled\"; }",
+            "original": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"visible\" | \"selectedFeature\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedFeatureIndex\" | \"selectedDrillInFeature\" | \"selectedFeatureComponent\" | \"currentAlignment\" | \"dockEnabled\"; }",
+            "resolved": "{ name: \"state\" | \"active\" | \"collapsed\" | \"featureCount\" | \"visible\" | \"selectedFeature\" | \"featureMenuOpen\" | \"features\" | \"promises\" | \"selectedFeatureIndex\" | \"selectedDrillInFeature\" | \"selectedFeatureComponent\" | \"currentAlignment\" | \"dockEnabled\"; }",
             "references": {}
           },
           "cancelable": true,
@@ -37036,8 +37473,25 @@
           },
           "cancelable": true,
           "composed": true,
-          "docs": "",
-          "docsTags": []
+          "docs": "Fires after the user clicks on an action in the Popup component.\nThis event may be used to define a custom function to execute when particular actions are clicked.",
+          "docsTags": [
+            {
+              "name": "see",
+              "text": "[actions](#actions)"
+            },
+            {
+              "name": "see",
+              "text": "[PopupTemplate.actions](https://developers.arcgis.com/javascript/latest/api-reference/esri-PopupTemplate.html#actions)"
+            },
+            {
+              "name": "see",
+              "text": "[open()](#open)"
+            },
+            {
+              "name": "example",
+              "text": "```js\nviewElement.addEventListener(\"arcgisViewClick\", (event) => {\n  const { mapPoint } = event.detail;\n  popupComponent.open({\n    location: mapPoint,\n    fetchFeatures: true,\n    actions: [{\n      // This text is displayed as a tooltip\n      title: \"Zoom out\",\n      // The ID used to reference this action in the event handler\n      id: \"zoom-out\",\n      // Sets the icon font used to style the action button\n      icon: \"magnifying-glass-minus\"\n    },\n    {\n      title: \"Delete Feature\",\n      id: \"delete-feature-action\",\n      icon: \"trash\"\n    }]\n  });\n});\n\n// Fires each time an action is clicked\nreactiveUtils.on(()=> popupComponent, \"arcgisTriggerAction\", (event)=>{\n  // If the zoom-out action is clicked, execute the following code\n  if(event.detail.action.id === \"zoom-out\"){\n    // Zoom out two levels (LODs)\n    viewElement.goTo({\n      center: viewElement.center,\n      zoom: viewElement.zoom - 2\n    });\n  }\n});\n```"
+            }
+          ]
         }
       ],
       "styles": [],
@@ -37747,7 +38201,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view from which Print will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Print-PrintViewModel.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisPrint component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -38173,7 +38627,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view from which the widget will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-ScaleBar-ScaleBarViewModel.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisScaleBar component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -38401,7 +38855,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon displayed in the widget's button.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -38727,7 +39181,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The current state of the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-ScaleRangeSlider-ScaleRangeSliderViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -38769,7 +39223,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-ScaleRangeSlider.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisScaleRangeSlider component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -41432,22 +41886,22 @@
       ],
       "styles": [
         {
-          "name": "--arcgis-layout-padding-top",
+          "name": "--arcgis-layout-overlay-space-top",
           "annotation": "prop",
           "docs": "Specifies the top padding for the layout."
         },
         {
-          "name": "--arcgis-layout-padding-bottom",
+          "name": "--arcgis-layout-overlay-space-bottom",
           "annotation": "prop",
           "docs": "Specifies the bottom padding for the layout."
         },
         {
-          "name": "--arcgis-layout-padding-left",
+          "name": "--arcgis-layout-overlay-space-left",
           "annotation": "prop",
           "docs": "Specifies the left padding for the layout."
         },
         {
-          "name": "--arcgis-layout-padding-right",
+          "name": "--arcgis-layout-overlay-space-right",
           "annotation": "prop",
           "docs": "Specifies the right padding for the layout."
         }
@@ -42383,7 +42837,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The current state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Search-SearchViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -42488,7 +42942,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Search-SearchViewModel.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisSearch component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "default": "null",
           "values": [
@@ -43408,8 +43862,13 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the component. Typically used when the component is controlled by another component (e.g. by the Expand component).\n\nSee also: [Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)",
-          "docsTags": [],
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
+          "docsTags": [
+            {
+              "name": "see",
+              "text": "[Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)"
+            }
+          ],
           "default": "\"measure-building-height-shadow\"",
           "values": [
             {
@@ -43659,7 +44118,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A reference to the [View](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-ShadowCast.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisShadowCast component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -44582,7 +45041,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -44643,15 +45102,20 @@
         },
         {
           "name": "layer",
-          "type": "GraphicsLayer",
+          "type": "GraphicsLayer | MapNotesLayer",
           "complexType": {
-            "original": "GraphicsLayer",
-            "resolved": "GraphicsLayer",
+            "original": "GraphicsLayer | MapNotesLayer",
+            "resolved": "GraphicsLayer | MapNotesLayer",
             "references": {
               "GraphicsLayer": {
                 "location": "import",
                 "path": "@arcgis/core/interfaces.d.ts",
                 "id": "notImplemented"
+              },
+              "MapNotesLayer": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
               }
             }
           },
@@ -44659,7 +45123,14 @@
           "reflectToAttr": false,
           "docs": "The [GraphicsLayer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-GraphicsLayer.html) associated with the Sketch widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Sketch.html#layer)",
           "docsTags": [],
-          "values": [],
+          "values": [
+            {
+              "type": "GraphicsLayer"
+            },
+            {
+              "type": "MapNotesLayer"
+            }
+          ],
           "optional": true,
           "required": false
         },
@@ -45032,7 +45503,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The Sketch widget's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Sketch.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -45158,7 +45629,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Sketch.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisSketch component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -46057,7 +46528,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisSlice component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -46548,7 +47019,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The current state of the Swipe.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Swipe-SwipeViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -46634,7 +47105,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Swipe-SwipeViewModel.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisSwipe component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -47008,7 +47479,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -47061,6 +47532,40 @@
           "optional": true,
           "required": false
         },
+        {
+          "name": "map",
+          "type": "Map | WebMap",
+          "complexType": {
+            "original": "Map | WebMap",
+            "resolved": "Map | WebMap",
+            "references": {
+              "Map": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              },
+              "WebMap": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "mutable": true,
+          "reflectToAttr": false,
+          "docs": "A reference to a [map](https://developers.arcgis.com/javascript/latest/api-reference/esri-Map.html) containing the tables.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-TableList.html#map)",
+          "docsTags": [],
+          "values": [
+            {
+              "type": "Map"
+            },
+            {
+              "type": "WebMap"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
         {
           "name": "minDragEnabledItems",
           "type": "number",
@@ -47416,7 +47921,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-TableList-TableListViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -47472,6 +47977,48 @@
           "values": [],
           "optional": true,
           "required": false
+        },
+        {
+          "name": "view",
+          "type": "LinkChartView | MapView | SceneView",
+          "complexType": {
+            "original": "LinkChartView | MapView | SceneView",
+            "resolved": "LinkChartView | MapView | SceneView",
+            "references": {
+              "LinkChartView": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              },
+              "MapView": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              },
+              "SceneView": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "mutable": true,
+          "reflectToAttr": false,
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisTableList component will be associated with a map or scene component rather than using the `view` property.",
+          "docsTags": [],
+          "values": [
+            {
+              "type": "LinkChartView"
+            },
+            {
+              "type": "MapView"
+            },
+            {
+              "type": "SceneView"
+            }
+          ],
+          "optional": true,
+          "required": false
         }
       ],
       "methods": [
@@ -47764,7 +48311,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -48028,7 +48575,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-TimeSlider-TimeSliderViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -48211,7 +48758,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "A reference to the [MapView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html) or [SceneView](https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html).\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-TimeSlider.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisTimeSlider component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -49003,8 +49550,13 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "",
-          "docsTags": [],
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
+          "docsTags": [
+            {
+              "name": "see",
+              "text": "[Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)"
+            }
+          ],
           "default": "\"compass-north-circle\"",
           "values": [
             {
@@ -49330,7 +49882,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the widget.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-Track-TrackViewModel.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisTrack component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {
@@ -49753,7 +50305,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon displayed in the widget's button.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -50261,7 +50813,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view associated with the UtilityNetworkAssociations widget instance.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-UtilityNetworkAssociations.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisUtilityNetworkAssociations component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -50749,7 +51301,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon displayed in the widget's button.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -51043,7 +51595,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-UtilityNetworkTrace-UtilityNetworkTraceViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -51112,7 +51664,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view from which the widget will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-UtilityNetworkTrace.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisUtilityNetworkTrace component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -51582,7 +52134,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The viewModel's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-UtilityNetworkTraceAnalysis-UtilityNetworkTraceAnalysisViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -51609,6 +52161,28 @@
           ],
           "optional": true,
           "required": false
+        },
+        {
+          "name": "view",
+          "type": "MapView",
+          "complexType": {
+            "original": "MapView",
+            "resolved": "MapView",
+            "references": {
+              "MapView": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "mutable": true,
+          "reflectToAttr": false,
+          "docs": "The view from which the widget will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-UtilityNetworkTraceAnalysis-UtilityNetworkTraceAnalysisViewModel.html#view)",
+          "docsTags": [],
+          "values": [],
+          "optional": true,
+          "required": false
         }
       ],
       "methods": [
@@ -51914,6 +52488,229 @@
       "parts": [],
       "listeners": []
     },
+    {
+      "filePath": "src/components/utility-network-trace-analysis/components/utility-network-trace-inputs/utility-network-trace-inputs.tsx",
+      "tag": "arcgis-utility-network-trace-inputs",
+      "overview": "",
+      "readme": "",
+      "usage": {},
+      "docs": "This is a sub-component used by the **ArcgisUtilityNetworkTraceAnalysis** component.\n\nThis sub-component takes a map view as an input.\nIt allows users to select utility networks, trace configurations, and input features for tracing.",
+      "docsTags": [
+        {
+          "name": "since",
+          "text": "4.34"
+        },
+        {
+          "name": "internal"
+        },
+        {
+          "name": "superclass",
+          "text": "{\"name\":\"LitElement\",\"package\":\"@arcgis/lumina\"}"
+        }
+      ],
+      "encapsulation": "shadow",
+      "dependents": [],
+      "dependencies": [],
+      "dependencyGraph": {},
+      "props": [
+        {
+          "name": "referenceElement",
+          "type": "HTMLArcgisLinkChartElement | HTMLArcgisMapElement | HTMLArcgisSceneElement | string",
+          "complexType": {
+            "original": "HTMLArcgisLinkChartElement | HTMLArcgisMapElement | HTMLArcgisSceneElement | string",
+            "resolved": "HTMLArcgisLinkChartElement | HTMLArcgisMapElement | HTMLArcgisSceneElement | string",
+            "references": {
+              "HTMLArcgisLinkChartElement": {
+                "location": "local",
+                "path": "index.js",
+                "id": "notImplemented"
+              },
+              "HTMLArcgisMapElement": {
+                "location": "local",
+                "path": "index.js",
+                "id": "notImplemented"
+              },
+              "HTMLArcgisSceneElement": {
+                "location": "local",
+                "path": "index.js",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "mutable": true,
+          "attr": "reference-element",
+          "reflectToAttr": false,
+          "docs": "By assigning the `id` attribute of the Map or Scene component to this property, you can position a child component anywhere in the DOM while still maintaining a connection to the Map or Scene.",
+          "docsTags": [
+            {
+              "name": "see",
+              "text": "[Associate components with a Map or Scene component](https://developers.arcgis.com/javascript/latest/programming-patterns/#associate-components-with-a-map-or-scene-component)"
+            }
+          ],
+          "values": [
+            {
+              "type": "HTMLArcgisLinkChartElement"
+            },
+            {
+              "type": "HTMLArcgisMapElement"
+            },
+            {
+              "type": "HTMLArcgisSceneElement"
+            },
+            {
+              "type": "string"
+            }
+          ],
+          "optional": true,
+          "required": false
+        },
+        {
+          "name": "selectedTraceConfiguration",
+          "type": "NamedTraceConfiguration",
+          "complexType": {
+            "original": "NamedTraceConfiguration",
+            "resolved": "NamedTraceConfiguration",
+            "references": {
+              "NamedTraceConfiguration": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "mutable": true,
+          "reflectToAttr": false,
+          "docs": "",
+          "docsTags": [],
+          "values": [],
+          "optional": true,
+          "required": false
+        },
+        {
+          "name": "selectedUtilityNetwork",
+          "type": "UtilityNetwork",
+          "complexType": {
+            "original": "UtilityNetwork",
+            "resolved": "UtilityNetwork",
+            "references": {
+              "UtilityNetwork": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "mutable": true,
+          "reflectToAttr": false,
+          "docs": "",
+          "docsTags": [],
+          "values": [],
+          "optional": true,
+          "required": false
+        },
+        {
+          "name": "view",
+          "type": "MapView | undefined",
+          "complexType": {
+            "original": "MapView | undefined",
+            "resolved": "MapView | undefined",
+            "references": {
+              "MapView": {
+                "location": "import",
+                "path": "@arcgis/core/interfaces.d.ts",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "mutable": true,
+          "reflectToAttr": false,
+          "docs": "",
+          "docsTags": [
+            {
+              "name": "required"
+            }
+          ],
+          "values": [
+            {
+              "type": "MapView"
+            },
+            {
+              "type": "undefined"
+            }
+          ],
+          "optional": false,
+          "required": true
+        }
+      ],
+      "methods": [
+        {
+          "name": "componentOnReady",
+          "returns": {
+            "type": "Promise<void>",
+            "docs": ""
+          },
+          "complexType": {
+            "signature": "(): Promise<void>",
+            "parameters": [],
+            "return": "Promise<void>",
+            "references": {
+              "Promise": {
+                "location": "import",
+                "path": "typescript/lib/lib.es5.d.ts",
+                "id": "notImplemented"
+              }
+            }
+          },
+          "signature": "componentOnReady(): Promise<void>",
+          "parameters": [],
+          "docs": "Create a promise that resolves once component is fully loaded.",
+          "docsTags": [
+            {
+              "name": "example",
+              "text": "```js\nconst arcgisUtilityNetworkTraceInputs = document.querySelector(\"arcgis-utility-network-trace-inputs\");\ndocument.body.append(arcgisUtilityNetworkTraceInputs);\nawait arcgisUtilityNetworkTraceInputs.componentOnReady();\nconsole.log(\"arcgis-utility-network-trace-inputs is ready to go!\");\n```"
+            },
+            {
+              "name": "inheritedFrom",
+              "text": "{\"name\":\"LitElement\",\"package\":\"@arcgis/lumina\"}"
+            }
+          ]
+        }
+      ],
+      "events": [
+        {
+          "event": "arcgisTraceInputsChange",
+          "detail": "void",
+          "bubbles": true,
+          "complexType": {
+            "original": "void",
+            "resolved": "void",
+            "references": {}
+          },
+          "cancelable": true,
+          "composed": true,
+          "docs": "",
+          "docsTags": []
+        },
+        {
+          "event": "arcgisUtilityNetworkChange",
+          "detail": "void",
+          "bubbles": true,
+          "complexType": {
+            "original": "void",
+            "resolved": "void",
+            "references": {}
+          },
+          "cancelable": true,
+          "composed": true,
+          "docs": "",
+          "docsTags": []
+        }
+      ],
+      "styles": [],
+      "slots": [],
+      "parts": [],
+      "listeners": []
+    },
     {
       "filePath": "src/components/utility-network-validate-topology/utility-network-validate-topology.tsx",
       "tag": "arcgis-utility-network-validate-topology",
@@ -51992,7 +52789,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon displayed in the widget's button.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -52146,7 +52943,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The view model's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-UtilityNetworkValidateTopology-UtilityNetworkValidateTopologyViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -52221,7 +53018,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "The view from which the widget will operate.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-UtilityNetworkValidateTopology.html#view)",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisUtilityNetworkValidateTopology component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -52579,7 +53376,7 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "Icon which represents the widget.",
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
           "docsTags": [
             {
               "name": "see",
@@ -53210,8 +54007,13 @@
           "mutable": true,
           "attr": "icon",
           "reflectToAttr": false,
-          "docs": "",
-          "docsTags": [],
+          "docs": "Icon which represents the component.\nTypically used when the component is controlled by another component (e.g. by the Expand component).",
+          "docsTags": [
+            {
+              "name": "see",
+              "text": "[Calcite Icons](https://developers.arcgis.com/calcite-design-system/icons/)"
+            }
+          ],
           "values": [
             {
               "type": "string"
@@ -53439,7 +54241,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The viewModel's state.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-VersionManagement-VersionManagementViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -53835,22 +54637,22 @@
       ],
       "styles": [
         {
-          "name": "--arcgis-layout-padding-top",
+          "name": "--arcgis-layout-overlay-space-top",
           "annotation": "prop",
           "docs": "Specifies the top padding for the layout."
         },
         {
-          "name": "--arcgis-layout-padding-bottom",
+          "name": "--arcgis-layout-overlay-space-bottom",
           "annotation": "prop",
           "docs": "Specifies the bottom padding for the layout."
         },
         {
-          "name": "--arcgis-layout-padding-left",
+          "name": "--arcgis-layout-overlay-space-left",
           "annotation": "prop",
           "docs": "Specifies the left padding for the layout."
         },
         {
-          "name": "--arcgis-layout-padding-right",
+          "name": "--arcgis-layout-overlay-space-right",
           "annotation": "prop",
           "docs": "Specifies the right padding for the layout."
         }
@@ -54225,7 +55027,7 @@
           "mutable": true,
           "attr": "state",
           "reflectToAttr": true,
-          "docs": "The state of the video layer.\n\n[Read more...](https://developers.arcgis.com/javascript/latest/api-reference/esri-widgets-VideoPlayer-VideoPlayerViewModel.html#state)",
+          "docs": "The current state of the component.",
           "docsTags": [
             {
               "name": "readonly",
@@ -54719,7 +55521,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisWeather component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [],
           "optional": true,
@@ -55107,7 +55909,7 @@
           },
           "mutable": true,
           "reflectToAttr": false,
-          "docs": "",
+          "docs": "The view associated with the component. \n  > **Note:** The recommended approach is to fully migrate applications to use map and scene components and avoid using MapView and SceneView directly. However, if you are migrating a large application from widgets to components, you might prefer a more gradual transition. To support this use case, the SDK includes this `view` property which connects a component to a MapView or SceneView. Ultimately, once migration is complete, the ArcgisZoom component will be associated with a map or scene component rather than using the `view` property.",
           "docsTags": [],
           "values": [
             {