@arcgis/map-components 5.1.0-next.77 → 5.1.0-next.78

package/dist/components/arcgis-presentation/customElement.d.ts

@@ -47,22 +47,29 @@ export abstract class ArcgisPresentation extends LitElement {
    * @default false
    */
   accessor keyboardNavigationEnabled: boolean;
-  /**
-   * Disable display of popup when slide with popup is applied.
-   * Per default the display of popup is disabled.
-   * The events arcgisPopupFeaturesRetrieved and arcgisPopupFeatureNotFound will be emitted also when popups are disabled.
-   *
-   * @default false
-   */
-  accessor popupDisabled: boolean;
   /**
    * specifies the size of the component
    *
    * @default "m"
    */
   accessor scale: "l" | "m" | "s";
+  /**
+   * Disable display of captions when slide is applied.
+   * Per default the display of captions is enabled.
+   *
+   * @default false
+   */
+  accessor slideCaptionsDisabled: boolean;
   /** The id of the slide applied to the view */
   accessor slideId: string | undefined;
+  /**
+   * Disable display of popup when slide with popup is applied.
+   * Per default the display of popup is enabled.
+   * The events arcgisPopupFeaturesRetrieved and arcgisPopupFeatureNotFound will be emitted also when popups are disabled.
+   *
+   * @default false
+   */
+  accessor slidePopupDisabled: boolean;
   /**
    * The view associated with the component. 
    *   > **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 arcgis-presentation component will be associated with a map or scene component rather than using the `view` property.