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

[sap.m.MessageStrip] Feature Request: Simplify announcement of message strips #4032

Closed
swendlandt opened this issue Apr 25, 2024 · 1 comment

Comments

@swendlandt
Copy link
Contributor

swendlandt commented Apr 25, 2024

OpenUI5 version: 1.123

Currently the official way to announce a dynamically generated MessageStrip for Screen Reader users is to call sap.ui.core.InvisibleMessage, see https://ui5.sap.com/#/api/sap.m.MessageStrip%23overview and the example https://ui5.sap.com/#/entity/sap.m.MessageStrip/sample/sap.m.sample.DynamicMessageStripGenerator/code.

Idea to make this easier for the user of the MessageStrip control:

Add a live property to the MessageStrip, e.g. when we add a MessageStrip we could do:

oMsgStrip = new MessageStrip("msgStrip", {
    live: true
});

Let’s say when the “live”-property is set on the MessageStrip and the MessageStrip detects that it becomes visible (I guess this can be done in onAfterRendering hook or in setVisible, not sure what would be the best place), then the MessageStrip can internally call the InvisibleMessage and add the announcement.

So technically it is the same as it is currently but instead of requiring the application to set the message the functionality would be encapsulated in the control. Of course, the consuming application would still need to set the property but it would be visible as part of the official API reference then. If a user of the control would not want to have the standard announcement, they still can leave the property false and implement the announcement themselves using the InvisibleMessage API directly.

@NHristov-sap
Copy link
Contributor

Hi @swendlandt ,

I have contached the responsible team and they told me that this feature request is already evaluated and communicated and they have given their opinions why they don't want to do it.

So feel free to contribute to the project with the feature you want.

Best Regards,
Nikolay Hristov
UI5 GitHub Dispatcher

@i556484 i556484 closed this as not planned Won't fix, can't repro, duplicate, stale May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants