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
Whenever any of the polaris components implement a button group with a primary & secondary action, they always have the secondary action first followed by the primary action but in case of the card component it has been implemented the other way around
Expected behavior
The secondaryFooterAction should be rendered first followed by the primaryFooterAction
Actual behavior
The primaryFooterActionis rendered before the secondaryFooterAction.
Issue summary
Whenever any of the polaris components implement a button group with a primary & secondary action, they always have the secondary action first followed by the primary action but in case of the card component it has been implemented the other way around
Expected behavior
The
secondaryFooterAction
should be rendered first followed by theprimaryFooterAction
Actual behavior
The
primaryFooterAction
is rendered before thesecondaryFooterAction
.Steps to reproduce the problem
Implement a card with footer actions as shown in https://codesandbox.io/s/yvwy63yll9?module=App.js
Specifications
I'd be happy to raise a PR for this if this is indeed a bug.
The text was updated successfully, but these errors were encountered: