Description
When size="large" is set on the DateTimePicker, the nested calendar and time-selector correctly render at their large dimensions, but the surrounding popup wrapper element does not receive the matching large-size CSS class, so it keeps its medium-size width. The enlarged calendar/time content then overflows and appears clipped.
Steps To Reproduce
- Open the following public demo: https://demos.telerik.com/kendo-angular-ui/demos/dateinputs/datetimepicker/appearance-size?theme=meridian-main
- Set the DateTimePicker
size to large.
- Open the popup and observe the calendar and time tabs.
Screenshots or video
Actual Behavior
A DateTimePicker with size="large" breaks the time selector rendering.
Expected Behavior
A DateTimePicker with size="large" should render its calendar and time selector correctly.
Suggested fix pointer:
The popup wrapper does not receive a rendering class tied to the picker's configured size (e.g., k-datetime-wrap-lg), so it cannot pick up the size-specific styling kendo-themes already provides. The wrapper's size-related class binding should be revisited so it also reflects the component's own size input, consistent with how size is already propagated to the nested calendar/time-selector.
Description
When
size="large"is set on the DateTimePicker, the nested calendar and time-selector correctly render at their large dimensions, but the surrounding popup wrapper element does not receive the matching large-size CSS class, so it keeps its medium-size width. The enlarged calendar/time content then overflows and appears clipped.Steps To Reproduce
sizetolarge.Screenshots or video
Actual Behavior
A DateTimePicker with
size="large"breaks the time selector rendering.Expected Behavior
A DateTimePicker with
size="large"should render its calendar and time selector correctly.Suggested fix pointer:
The popup wrapper does not receive a rendering class tied to the picker's configured
size(e.g.,k-datetime-wrap-lg), so it cannot pick up the size-specific stylingkendo-themesalready provides. The wrapper's size-related class binding should be revisited so it also reflects the component's ownsizeinput, consistent with how size is already propagated to the nested calendar/time-selector.