You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But BarcodeScannerDialog, which is new feature of 1.24.0, allows only ref to open the dialog.
It's not consistent, and is giving confession to old users.
Describe the solution you'd like
Please add 'open' property in BarcodeScannerDialog and allows opening/closing the component using that property.
Describe alternatives you've considered
No response
Additional Context
No response
Declaration
I’m not disclosing any internal or sensitive information.
The text was updated successfully, but these errors were encountered:
* feat(ui5-barcode-scanner-dialog): add 'open' property
This change introduces a new `open` property to the
`ui5-barcode-scanner-dialog` component, enhancing the control over the
dialog's visibility. This feature aligns with the behavior of other
similar components, providing a more consistent user experience.
Related: #8072
* feat(ui5-barcode-scanner-dialog): add 'open' property
This change introduces a new `open` property to the
`ui5-barcode-scanner-dialog` component, enhancing the control over the
dialog's visibility. This feature aligns with the behavior of other
similar components, providing a more consistent user experience.
Related: #8072
Uh oh!
There was an error while loading. Please reload this page.
Is your feature request related to a problem?
Dialog can be opened with 'open' property and is recommended since 0.22.0, as the document says : https://sap.github.io/ui5-webcomponents-react/?path=/docs/modals-popovers-dialog--docs
But BarcodeScannerDialog, which is new feature of 1.24.0, allows only ref to open the dialog.
It's not consistent, and is giving confession to old users.
Describe the solution you'd like
Please add 'open' property in BarcodeScannerDialog and allows opening/closing the component using that property.
Describe alternatives you've considered
No response
Additional Context
No response
Declaration
The text was updated successfully, but these errors were encountered: