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
Check the demo and open the DevTools to inspect the order of the action buttons.
What is the motivation or use case for changing the behavior?
In ThemeBuilder, we use KendoReact to render the components. There, the order of the buttons is as explained in this issue. However, in other technologies where the issue does not persist (for example, in Blazor), the order is different. Users may want to change this behavior in ThemeBuilder by setting flex-direction: row-reverse, but once they decide to import the theme generated through ThemeBuilder in their application, the result will be unexpected to them.
Reported through t.1668996.
The text was updated successfully, but these errors were encountered:
I'm submitting a...
Current behavior
The Set button appears after the Cancel button.
However, according to the Rendering truth, the Set button should appear before the Cancel button.
Expected behavior
The Set button to appear before the Cancel button.
Minimal reproduction of the problem with instructions
What is the motivation or use case for changing the behavior?
In ThemeBuilder, we use KendoReact to render the components. There, the order of the buttons is as explained in this issue. However, in other technologies where the issue does not persist (for example, in Blazor), the order is different. Users may want to change this behavior in ThemeBuilder by setting flex-direction: row-reverse, but once they decide to import the theme generated through ThemeBuilder in their application, the result will be unexpected to them.
Reported through t.1668996.
The text was updated successfully, but these errors were encountered: