[Feature Request]: Loading property behaviour in appropriate in ui5-combobox and ui5-multi-combobox
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 285
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 59
Description
Feature Request Description
Impacted components: ui5-combobox and ui5-multi-combobox
Loading property behaviour is bit confusing, when loading property is true, what does this signify
- loading only shows up if the list is empty(?)
- loading shows up at the end of the list (“scroll-to-load”)
- loading indicator is shown on a semi-transparent black background
I guess, it is rather the 3rd entry, it's randomly shows loading on top of the dropdown items.
The busy indicator should not occupy the whole available height of the responsive popover over the drop-down items in the background, like in the above image. Rather it should much smaller and independent of the height of the responsive popover height and width.
Proposed Solution
As part of the solution, it would be more accurate if the loading or busy status should be shown in much smaller size without, depending on the size of the responsive popover. This is exact implementation in SAP UI5 control, where the loading/busy state would look like below:
Proposed Alternatives
No response
Organization
Ariba
Additional Context
No response
Priority
None
Privacy Policy
- I’m not disclosing any internal or sensitive information.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the loading-property behavior of ui5-combobox and ui5-multi-combobox, then review how their responsive popovers display the loading indicator. Done means the loading or busy state is shown as a smaller indicator independent of the popover’s full height and width, matching the proposed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100