Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: MultiCombobox with loading prop #10581

Open
1 task done
skowrons opened this issue Jan 17, 2025 · 2 comments
Open
1 task done

[Feature Request]: MultiCombobox with loading prop #10581

skowrons opened this issue Jan 17, 2025 · 2 comments

Comments

@skowrons
Copy link

Feature Request Description

The current Combobox component includes a loading prop, which enables a loading indicator to signal a loading state. However, the MultiCombobox does not provide a similar API, resulting in inconsistent handling of the loading state across components. For improved developer experience and API consistency, the MultiCombobox should support the same loading prop.

Proposed Solution

  • Add a loading prop to the MultiCombobox component, mirroring the behavior and API of the Combobox's loading state.
  • Optionally, introduce a delay prop to control the BusyIndicator behavior, allowing for customizable delay times before showing the loading indicator.
  • Expand support for the loading prop to the Select and MultiSelect components to ensure consistent loading state handling across all similar components in the library.

Proposed Alternatives

If aligning the API across components is not feasible or desired, consider removing the loading prop from the Combobox component to maintain consistency and avoid API discrepancies (with 3.0.0).

Organization

No response

Additional Context

No response

Priority

Low

Privacy Policy

  • I’m not disclosing any internal or sensitive information.
@IlianaB
Copy link
Member

IlianaB commented Jan 17, 2025

Hello @SAP/ui5-webcomponents-topic-rl , take a look of this feature request.

@hristop
Copy link
Contributor

hristop commented Jan 17, 2025

Hi @skowrons ,

Thanks for bringing this topic to our attention.
As the current design specification does not contain such feature it will have to go though the Inner Source process. Could you please raise a feature BLI to the Central Design team so that they can look into it and provide us with the proper specification?
Once you do so, can you please add the BLI number here for reference?

Best Regards,
Hristo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

3 participants