Tags: ClickHouse/click-ui
Tags
fix(Tooltip): render above the overlay tier so tooltips aren't occlud… …ed (#1153) Tooltip content had no z-index, while Dropdown, Menu, ContextMenu and DatePicker set `z-index: 1`. A tooltip whose trigger sits inside one of those overlays (e.g. an EllipsisContent in a Dropdown) therefore rendered behind it. Give tooltip content `z-index: 2` so it sits above that tier. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
feat(DateRangePicker): add allowOnlyDatesList prop to restrict select… …able dates (#1146) * feat(DateRangePicker): add allowOnlyDatesList prop to restrict selectable dates * feat(DatePicker): simplify date restriction logic using isDateNotInAllowList * feat(DatePicker): add tests for isDateNotInAllowList function and improve its implementation * test(DatePicker): format isDateNotInAllowList test for better readability
fix(Flyout): remove container gap that doubled section spacing (#1102) PR #1095 added a semicolon to the padding declaration, which activated a previously-dead `gap` on FlyoutContent. Section spacing has always come from the separators' own margins (Separator size), so the gap stacked on top of those margins and doubled the spacing between the header, body, and footer. Set the container gap to 0 so spacing matches the design. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
fix(Container): keep base styles overridable by styled-components (#1101 ) Since Container migrated to CSS Modules, its base `.container` rule began beating equal-specificity `styled(Container)` overrides of layout properties such as `padding` and `gap`. A downstream `styled(Flyout.Header)` padding override (e.g. control-plane's sidebar header) was silently dropped, and Flyout itself needed an `&&` specificity hack just to apply its own padding. Scope the base rule with `:where(.container)` so it sits at zero specificity. Modifier classes (`.container_padding_md`, …) and consumer overrides now win naturally without a hack. Rendering is unchanged — modifier classes already won over the base by source order. The temporary `&&` workaround in Flyout's Element/Header/Footer is removed. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
fix(Icon): enlarge check glyph to fill its viewBox The `check` glyph was small and offset within its 24x24 viewBox, so it rendered noticeably smaller than other icons. Scale the path up ~1.25x about the viewBox center; stroke weight stays at 2. Render the Checkbox's check at 0.8rem (= 1rem / 1.25) so the checkmark inside the box keeps its current size; the indeterminate (minus) icon is unaffected. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
fix(Container): stop nested Container inheriting layout custom proper… …ties The CSS Modules migration forwards optional layout props (fillHeight, grow, shrink, minHeight, maxHeight, overflow) to the DOM as CSS custom properties, emitted inline only when the prop is set. Custom properties inherit by default, so a nested Container that omits those props inherited its ancestor's values — e.g. a layout root with `fillHeight` forced `height: 100%` onto every descendant Container (observed as the control-plane alert banner stretching to fill the viewport, with knock-on spacing breakage throughout the page). Reset these custom properties to `initial` on the base `.container` rule so a declaration on the element wins over inheritance, and add `var()` fallbacks matching the styled-components defaults. Verified in a browser: with the bug a child Container inherited flex-grow:1/height:198px/overflow:hidden; after the fix it hugs its content (flex-grow:0, height:34px, overflow:visible). Adds a NestedInheritance story and a computed-style regression test; all 30 existing Container visual snapshots are unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
PreviousNext