-
Notifications
You must be signed in to change notification settings - Fork 70
Closed
Labels
BugSomething isn't workingSomething isn't working
Milestone
Description
Describe the bug
There are two discrepancies in the DateTimePicker rendering that have been flagged:
- In the default rendering of the DateTimePicker component the action buttons have two extra classes
k-time-accept
andk-time-cancel
which are not present in the adaptive rendering.
While these classes have no styles associated with them, they have use cases across the suites.
- The order of the action buttons in the Adaptive test is wrong since the primary button should always be first
To reproduce
- Navigate to the provided links showcasing the rendering and inspect the action buttons
- Notice that the aforementioned classes are missing and the order of the buttons is wrong in the DateTimePicker-adaptive test
Expected behavior
Both classes and action button order should match in both tests
Metadata
Metadata
Assignees
Labels
BugSomething isn't workingSomething isn't working