-
Notifications
You must be signed in to change notification settings - Fork 43
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Storage: show skeletons only when needed (#1171)
## Problem - The loading skeletons are displayed always, even when not needed - The installation device selection popup is empty when clicked quickly before loading all data ## Solution ### Loading Skeletons - Pass the name of the component which is changed by user to parent - Send back the changing component to all children - There is mapping which defined whether a child needs refresh when some setting is being changed ### Installation Device Progress - Use the sent data when when the stored values are `undefined` - Show a simple skeleton ### screenreaderText Properties - I have removed all `screenreaderText` properties for skeletons and keep it only for the result section - The reason is that it does not make sense to notify users about 5 values in progress, it usually takes about 2 seconds to refresh the data so the screen reader would not have enough time to read all messages - Use it only the result section which is refreshed always, moreover the data for the other values will be read together with the result data, they will always take the same time ## Questions - Do we need more granularity with changing values? I.e. if the Btrfs snapshots are enabled/disabled then the partition list below is refresh as well. (IMHO fine to solve this later in a separate card / PR.) - Better progress for the installation device loading? (Note: do not overengineer here, the progress is displayed only when you click the link very quickly after opening the storage page, in most cases it won't be used at all.) ## Testing - Tested manually ## Screenshots When enabling/disabling the Btrfs snapshots all data was refreshed, now the installation device and the space policy does not show the progress skeletons. | Original | Fixed | |---|---| | ![storage_skeletons_broken](https://github.com/openSUSE/agama/assets/907998/9833814b-ee02-42c3-be7f-089f4b832cba) | ![storage_skeletons_fixed](https://github.com/openSUSE/agama/assets/907998/0c695214-3804-42ee-b14d-4af64d74fdd3) | Another fix was empty installation device screen when the "Installation device" link was clicked quickly, before loading the data finished. | Original | Fixed | |---|---| | ![storage_loading_progress_broken](https://github.com/openSUSE/agama/assets/907998/70b7fd46-63f5-44ec-b5b7-63a4de0ffa81) | ![storage_loading_progress2](https://github.com/openSUSE/agama/assets/907998/c7989b53-b116-4264-92e3-f48cc69d671f) |
- Loading branch information
Showing
13 changed files
with
170 additions
and
37 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.