-
Notifications
You must be signed in to change notification settings - Fork 4.8k
DataViews: keep old data while new data is loading #69194
Copy link
Copy link
Closed
Labels
[Feature] DataViewsWork surrounding upgrading and evolving views in the site editor and beyondWork surrounding upgrading and evolving views in the site editor and beyond[Status] In ProgressTracking issues with work in progressTracking issues with work in progress[Type] FeatureNew feature to highlight in changelogs.New feature to highlight in changelogs.
Metadata
Metadata
Assignees
Labels
[Feature] DataViewsWork surrounding upgrading and evolving views in the site editor and beyondWork surrounding upgrading and evolving views in the site editor and beyond[Status] In ProgressTracking issues with work in progressTracking issues with work in progress[Type] FeatureNew feature to highlight in changelogs.New feature to highlight in changelogs.
Type
Fields
Give feedbackNo fields configured for issues without a type.
What
The DataViews component has a
isLoadingprop that enables consumers to build this user experience (displays spinner when data is loading):Screen.Recording.2025-02-13.at.23.22.39.mov
In certain scenarios, consumers want to build this other experience (keep old data until new data has been loaded):
Screen.Recording.2025-02-13.at.23.19.55.mov
Discussion
There's an existing
aria-busyattribute attached to the table to communicate the loading state to Assistive Technologies. However, it's not used or can't be configured to communicate the same to visual users.The second experience can be built today doing the following:
aria-busyattribute to set a visual indication (e.g., lower opacity). This is hacky because the classes are not public API. It'd be best if we had an API-first way to do this:Goal
It'd be good to enable consumers to build the second experience as a first-class citizen in DataViews.