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
Hi team,
can you, please, take a look at the above comment and consider if it is applicable item for an enhancement request,
or it could be taken as a fix?
Thank you!
Best regards,
Petya Markova.
(UI5 Web components dispatcher)
The intention of ui5-dialog is to be as open as possible and have as few presumptions (such as having buttons in the footer) as possible.
Therefore, it is an intentional decision to provide a footer slot (semantics are the app passes a single element that serves as a footer, although technically one can pass multiple elements to any slot). If we were to change the alignment, making it easier for people to directly pass buttons (and skip the footer itself), the footer semantics would change from footer to footer item (such as a button). The "ideal" way to use the footer slot is to pass a single item (div/toolbar) with 100% width which regardless of alignment would take up the whole space.
As for the height, we discussed and agreed to pre-set the height of the footer to 2.5rem (Compact) or 2.75rem (Cozy). We are going to follow up with a PR for this.
Feature Request Description
I would like to have an easy way of placing a single button into the
footer
slot of theui5-dialog
and have the correct, Fiori compliant alignment.Proposed Solution
end
ui5-webcomponents/packages/main/src/themes/PopupsCommon.css
Lines 39 to 54 in 379cc7b
These changes would allow such a pattern:
which is in my opinion way more convenient than the current solution:
Proposed Alternatives
I could add a custom flex box or use the
ui5-bar
with theend-content
slot (but this would lead to incorrect paddings).Additional Context
Basically I want to have a similar behaviour to the
buttons
aggregation of thesap.m.Dialog
SAPUI5 Control:Priority
A clear and concise description of the impact/urgency of the required feature.
Stakeholder Info (if applicable)
The text was updated successfully, but these errors were encountered: