Skip to content

[Carousel] Add ability to hide pagination dots #11131

@macandcheese

Description

@macandcheese

Check existing issues

Which Component

Carousel

Description

For some complex implementations - the Carousel may be controlled by an external UI (increment arrows outside the Carousel area, a "filmstrip" that correspond to Carousel Items, etc.)

In these cases, the pagination dots may be unnecessary.

Acceptance Criteria

A configuration is added to not display the carousel dots. This should be mutually exclusive from the arrows - which may still be useful / desired in some cases.

Prop name
paginationDisabled (type: boolean, default: false)

Design

Image

>> Figma File <<

A11y

  • When paginationDisabled = true → remove bullet-related ARIA (e.g., aria-current, aria-label).
  • Consider providing alternate nav feedback, such as:
  • Visually hidden progress indicators. Example: aria-live region announcing the active slide (e.g., “Item 2 of 5”)

Example Use Case

Consider a use case like this, where a developer can control the active / selected Carousel Item from separate controls:

Screenshot 2024-12-21 at 12 26 00 PM

Here I'd like to hide the Carousel-rendered dots as I have another method of interaction (and I've already hidden the arrows with arrow-type.

Priority impact

impact - p3 - not time sensitive

Related Carousel Issues

#9104
#9209
#10193

Calcite package

  • @esri/calcite-components
  • @esri/calcite-components-react
  • @esri/calcite-design-tokens
  • @esri/eslint-plugin-calcite-components

Esri team

Calcite (design)

monday.com sync: #8745474746

Metadata

Metadata

Assignees

No one assigned

    Labels

    4 - installedIssues that have been merged to the "dev" branch and/or are ready for QA/QC.ArcGIS Maps SDK for JavaScriptIssues logged by ArcGIS SDK for JavaScript team members.Calcite (design)Issues logged by Calcite designers.c-carouselIssues that pertain to the calcite-carousel componentcalcite-componentsIssues specific to the @esri/calcite-components package.designIssues that need design consultation prior to, or during, development.enhancementIssues tied to a new feature or request.estimate - 2Small fix or update, may require updates to tests.estimate - design - sm1-4 days of design work.impact - p3 - not time sensitiveUser set priority impact status of p3 - not time sensitivep - highIssue should be addressed in the current milestone, impacts component or core functionality

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions