9.7.3
-
[@mantine/schedule]Add slotLabelInterval prop to DayView and WeekView to display time labels more often than once per hour -
[@mantine/schedule]Add option to customize business hours minutes and change colors -
[@mantine/schedule]MobileMonthView: AddwithWeekendDaysprop -
[@mantine/charts]Fix right Y axis children rendering (#9295) -
[@mantine/hooks]use-scroller: Fix next click being ignored after a drag ends by leaving the container (#9294) -
[@mantine/hooks]use-event-listener: Fix listener being removed after re-render when options object is passed inline (#9292) -
[@mantine/core]ScrollArea: Add --scrollarea-offset-size CSS variable (#9290) -
[@mantine/core]Cascader: Fix ArrowLeft and ArrowRight not being mirrored in RTL (#9286) -
[@mantine/hooks]use-throttled-callback: Handle reentrant calls (#9284) -
[@mantine/core]Radio, Chip: Fix readOnly prop not preventing value changes (#9282) -
[@mantine/core]Select: Fix onChange option argument type not including null (#9281) -
[@mantine/core]Switch: FixreadOnlyprop not preventing toggle (#9280) -
[@mantine/core]Fix searchable inputs ignoring typing when rendered in another window or iframe (#9278) -
[@mantine/hooks]use-focus-trap: Fix focus not being fully trapped when used with macOS Full Keyboard Access off
9.7.2
-
[@mantine/core]PinInput: Fix readOnly not preventing value changes on Delete, Backspace and paste (#9258) -
[@mantine/core]Divider: Addaria-orientation(#9259) -
[@mantine/core]Tooltip: Fix disabled tooltip settingaria-describedbyon its target (#9261) -
[@mantine/core]Transition: Fix frames and callbacks running after unmount during the first frame (#9263) -
[@mantine/hooks]use-scroll-into-view: Reset start time on cancel (#9265) -
[@mantine/core]Fix Backspace removing the last value when readOnly is set in MultiSelect and TreeSelect components (#9267) -
[@mantine/schedule]ResourcesDayView: Fix sticky resource labels covering the time labels row (#9268) -
[@mantine/hooks]use-debounced-callback: Avoid repeating completed leading calls (#9269) -
[@mantine/schedule]MobileMonthView: Fix multi-day event time display on start, middle and end days (#9272) -
[@mantine/form]AddUseContextFormtype export (#9275) -
[@mantine/form]Fix potential global prototype position -
[@mantine/tiptap]Add option to handle images pasted with other rich text elements in the image extension (#9270)
9.7.1
-
[@mantine/schedule]Fix startScrollTime scroll position (#9255) -
[@mantine/core]RollingNumber: Fix sub-pixel digit misalignment at fractional zoom levels (#9251) -
[@mantine/core]Tree: Add aria-expanded to tree items with children (#9247) -
[@mantine/core]SegmentedControl: Do not call Math.random during render (#9245) -
[@mantine/core]Popover: Add capture prop to control events capturing phase (#9243) -
[@mantine/form]Fix clearing state of unrelated fields (#9242) -
[@mantine/core]AngleSlider: Set aria-disabled on thumb when disabled (#9238) -
[@mantine/core]Combobox: Set aria-disabled on disabled Combobox.Option (#9236) -
[@mantine/form]Fix reorderListItem moving errors of items whose index shares a prefix with the reordered index (#9235) -
[@mantine/schedule]MonthView: Fix quadratic row assignment for weeks with many events (#9232) -
[@mantine/hooks]use-pagination: Fix single page being replaced with dots on the right side (#9229) -
[@mantine/core]ScrollArea: Fix wheel listener on document blocking compositor scrolling for the whole page (#9225) -
[@mantine/dates]DateTimePicker: Fix time not being limited by minDate and maxDate (#9221) -
[@mantine/core]Select, MultiSelect, Autocomplete, TagsInput: Fix listbox aria-labelledby referencing a missing label element (#9219) (#9220) -
[@mantine/hooks]use-debounced-state: Fix leading edge firing only once (#9214)
9.7.0
View changelog with demos on mantine.dev website
You can now sponsor Mantine development with OpenCollective. All funds are used to improve Mantine and create new features and components.
@mantine/mcp-server now exposes 406 documentation pages instead of 164. Previously only components were indexed – hooks, @mantine/form, styling, theming, guides and help.mantine.dev FAQ pages are now included as well. Changelog pages are deliberately excluded to keep search results focused on current APIs.
Documentation is now retrieved by section rather than by whole page. get_item_doc returns a page outline (description, import statement and the list of section headings) by default, a single section with the section argument, or the entire page with full: true. Requesting useForm this way returns about 1KB instead of 9KB, and the largest pages drop from roughly 89KB to 4KB.
Other improvements:
- New
get_apitool – resolves a symbol such asuseFormoruseDisclosureto its TypeScript signature and exported types without knowing which page documents it - Ranked search –
search_docsresults point at the specific section that matched, so a query like "validate a form with zod" resolves to thezodsection of the schema validation page - Search synonyms – queries now match the search keywords maintained in the documentation, so "command palette" finds Spotlight
- More filters –
list_itemsacceptsgroup,categoryandpackagein addition tokind - Hook signatures –
get_item_propsreturns the TypeScript signature for hooks, and points at the relevant section for pages that document their API in prose
The server was also migrated to the official Model Context Protocol SDK, so the protocol version is negotiated with the client instead of being pinned.
For setup details, supported tools, and client-specific instructions, see Mantine with LLMs.
New Tour component provides interactive step-by-step application onboarding. It highlights target elements with a spotlight overlay and displays tooltips with navigation controls. Supports both guided (sequential) and beacon (non-sequential) modes.
New Toolbar component provides an accessible toolbar container with roving tabindex keyboard navigation, toggle groups with single/multiple selection, visual grouping, and dividers. Styling is similar to RichTextEditor toolbar.
New Toggle component is a button that can be toggled between active and inactive states:
New JsonViewer component can be used to display complex JSON structures with expand/collapse, type indicators, copy to clipboard, and other features:
Checkbox and Radio components now support variant="light" – the indicator uses a light background color with a colored icon, similar to the light variant available in other components like Button:
import { Radio, Checkbox, Stack } from '@mantine/core';
function Demo() {
return (
<Stack gap={7}>
<Checkbox variant="light" label="Light Checkbox" defaultChecked />
<Checkbox variant="light" label="Light indeterminate Checkbox" indeterminate />
<Radio variant="light" label="Light Radio" defaultChecked />
</Stack>
);
}
RichTextEditor now supports image upload with loading states. Images can be uploaded via toolbar button, drag and drop, or paste. During upload, a local preview is shown with a loading indicator.
Configuring getUploadImageExtension is enough to enable uploads – onImageUpload and onImageUploadError props of RichTextEditor are optional overrides for the toolbar control. onImageUpload can resolve either to a string or to { src, alt, title } (new exported ImageUploadResult type) to set alternative text on the uploaded image. Several files picked, dropped or pasted together are inserted in the order they were selected and are undone as one step.
import TipTapImage from '@tiptap/extension-image';
import { useEditor } from '@tiptap/react';
import StarterKit from '@tiptap/starter-kit';
import { getUploadImageExtension, ImageUploadResult, RichTextEditor } from '@mantine/tiptap';
function handleImageUpload(file: File): Promise<ImageUploadResult> {
return new Promise((resolve) => {
setTimeout(() => {
resolve({ src: URL.createObjectURL(file), alt: file.name });
}, 3000);
});
}
function Demo() {
const editor = useEditor({
shouldRerenderOnTransaction: true,
extensions: [
StarterKit,
getUploadImageExtension(TipTapImage, { onImageUpload: handleImageUpload }),
],
content: '<p>Click the image button in the toolbar, or drag & drop / paste an image into the editor.</p>',
});
return (
<RichTextEditor editor={editor}>
<RichTextEditor.Toolbar>
<RichTextEditor.ControlsGroup>
<RichTextEditor.Bold />
<RichTextEditor.Italic />
</RichTextEditor.ControlsGroup>
<RichTextEditor.ControlsGroup>
<RichTextEditor.ImageUpload />
</RichTextEditor.ControlsGroup>
</RichTextEditor.Toolbar>
<RichTextEditor.Content />
</RichTextEditor>
);
}
DayView and WeekView now support eventOverlapMode prop that controls how events overlapping in time share the horizontal space. The default columns mode splits the available width evenly between them, which becomes unreadable once a large number of events overlap. The new cascade mode indents each event and stacks it over the previous one, so every event keeps a readable width no matter how many of them overlap.
The indent shrinks automatically as the group grows, so the event on top always keeps at least 60% of the available width. Covered events can still be read and used: rest the pointer on one and it is raised above the events covering it, which also makes its resize handles reachable. Keyboard users get the same result by focusing the event with Tab. eventOverlapRaiseDelay prop controls how long the pointer must rest on an event before it is raised, in milliseconds (600 by default).
import { useState } from 'react';
import { SegmentedControl, Stack } from '@mantine/core';
import { ScheduleEventOverlapMode, WeekView } from '@mantine/schedule';
import { events } from './data';
function Demo() {
const [mode, setMode] = useState<ScheduleEventOverlapMode>('cascade');
return (
<Stack>
<SegmentedControl
value={mode}
onChange={(value) => setMode(value as ScheduleEventOverlapMode)}
data={[
{ value: 'columns', label: 'columns' },
{ value: 'cascade', label: 'cascade' },
]}
/>
<WeekView
date={new Date()}
events={events}
startTime="08:00:00"
endTime="14:00:00"
eventOverlapMode={mode}
/>
</Stack>
);
}
All Schedule views can now reject a drag or resize before it is committed, based on where the event is being dropped rather than on which event is being dragged. Previously canDragEvent and canResizeEvent only decided whether an event was draggable or resizable at all, so the only way to prevent a double booking was to accept the drop, notice the conflict in the handler and not update state – which produced a snap-back with no explanation:
preventEventOverlaprejects placements that would make the event overlap another event. Pass a function to decide per pair of events: returntrueto forbid that particular overlap.canDropEventandcanResizeEventToare called before a drop or resize is committed – returnfalseto reject it.canDropExternalEventdoes the same for items dragged in from outside the schedule.onEventPlacementRejectedreports the rejection with the conflicting events and the reason.
The checks compose: a placement is allowed only when the overlap check passes and the matching callback returns a value other than false. The overlap check runs first, so onEventPlacementRejected can report conflicts without your code repeating the work. While the pointer is over an invalid target the drag ghost and the resizing event get data-invalid, so the rejection is visible before the pointer is released.
import { useState } from 'react';
import dayjs from 'dayjs';
import { Stack, Text } from '@mantine/core';
import { WeekView, ScheduleEventData } from '@mantine/schedule';
const startOfWeek = dayjs()
.subtract((dayjs().day() + 6) % 7, 'day')
.format('YYYY-MM-DD');
const initialEvents: ScheduleEventData[] = [
{
id: 1,
title: 'Standup',
start: `${startOfWeek} 09:00:00`,
end: `${startOfWeek} 09:30:00`,
color: 'blue',
},
{
id: 2,
title: 'Design review',
start: `${startOfWeek} 11:00:00`,
end: `${startOfWeek} 12:00:00`,
color: 'grape',
},
{
id: 3,
title: 'Retro',
start: `${startOfWeek} 14:00:00`,
end: `${startOfWeek} 15:00:00`,
color: 'teal',
},
];
function Demo() {
const [date, setDate] = useState(dayjs().format('YYYY-MM-DD'));
const [events, setEvents] = useState(initialEvents);
const [message, setMessage] = useState<string | null>(null);
return (
<Stack>
<WeekView
date={date}
onDateChange={setDate}
events={events}
startTime="08:00:00"
endTime="18:00:00"
withEventsDragAndDrop
withEventResize
eventDragInterval={15}
preventEventOverlap
onEventDrop={({ eventId, newStart, newEnd }) => {
setMessage(null);
setEvents((prev) =>
prev.map((event) =>
event.id === eventId ? { ...event, start: newStart, end: newEnd } : event
)
);
}}
onEventResize={({ eventId, newStart, newEnd }) => {
setMessage(null);
setEvents((prev) =>
prev.map((event) =>
event.id === eventId ? { ...event, start: newStart, end: newEnd } : event
)
);
}}
onEventPlacementRejected={(data) => {
if (data.action === 'external-drop') {
return;
}
setMessage(
`${data.event.title} cannot be ${data.action === 'drop' ? 'moved' : 'resized'} there – it would overlap ${data.conflicts
.map((conflict) => conflict.title)
.join(', ')}`
);
}}
/>
{message && <Text c="red" size="sm">{message}</Text>}
</Stack>
);
}
In resource views the conflict set is scoped to the target resource, so moving an event onto another resource row is checked against that row rather than the one it came from:
import { useState } from 'react';
import dayjs from 'dayjs';
import { Stack, Text } from '@mantine/core';
import { ResourcesDayView, ScheduleEventData, ScheduleResourceData } from '@mantine/schedule';
const today = dayjs().format('YYYY-MM-DD');
const resources: ScheduleResourceData[] = [
{ id: 'room-a', label: 'Room A' },
{ id: 'room-b', label: 'Room B' },
{ id: 'room-c', label: 'Room C (large groups only)' },
];
const initialEvents: ScheduleEventData[] = [
{
id: 1,
title: 'Interview (2 people)',
start: `${today} 09:00:00`,
end: `${today} 10:00:00`,
color: 'blue',
resourceId: 'room-a',
payload: { attendees: 2 },
},
{
id: 2,
title: 'All-hands (40 people)',
start: `${today} 11:00:00`,
end: `${today} 12:00:00`,
color: 'grape',
resourceId: 'room-c',
payload: { attendees: 40 },
},
];
function Demo() {
const [date, setDate] = useState(dayjs().format('YYYY-MM-DD'));
const [events, setEvents] = useState(initialEvents);
const [message, setMessage] = useState<string | null>(null);
return (
<Stack>
<ResourcesDayView
date={date}
onDateChange={setDate}
resources={resources}
events={events}
startTime="08:00:00"
endTime="18:00:00"
withEventsDragAndDrop
preventEventOverlap
canDropEvent={({ event, resourceId }) =>
resourceId !== 'room-c' || (event.payload?.attendees ?? 0) >= 20
}
onEventDrop={({ eventId, newStart, newEnd, resourceId }) => {
setMessage(null);
setEvents((prev) =>
prev.map((event) =>
event.id === eventId
? { ...event, start: newStart, end: newEnd, resourceId }
: event
)
);
}}
onEventPlacementRejected={(data) => {
if (data.action === 'external-drop') {
return;
}
setMessage(
data.reason === 'overlap'
? `${data.event.title} would overlap ${data.conflicts.length} event(s) in that room`
: 'Room C is reserved for meetings with 20 or more attendees'
);
}}
/>
{message && <Text c="red" size="sm">{message}</Text>}
</Stack>
);
}
TreeSelect now supports renderPill prop to customize how pills are rendered for selected values in multiple and checkbox modes, similar to renderPill prop of MultiSelect. The callback receives the tree node, so pills can use nodeProps or the node structure, for example to show a different icon for parent and leaf nodes:
import { FileTextIcon, FolderSimpleIcon } from '@phosphor-icons/react';
import { Group, Pill, TreeSelect, TreeSelectProps } from '@mantine/core';
import { data } from './data';
const renderTreePill: TreeSelectProps['renderPill'] = ({ node, onRemove, disabled, readOnly }) => (
<Pill withRemoveButton={!readOnly} onRemove={onRemove} disabled={disabled}>
<Group gap={4} wrap="nowrap">
{node.children || node.hasChildren ? (
<FolderSimpleIcon size={12} />
) : (
<FileTextIcon size={12} />
)}
{node.label}
</Group>
</Pill>
);
function Demo() {
return (
<TreeSelect
mode="checkbox"
checkedStrategy="parent"
label="Categories"
placeholder="Pick categories"
data={data}
defaultValue={['phones', 'headphones']}
defaultExpandAll
renderPill={renderTreePill}
/>
);
}
Tooltip now supports hideDetached prop, which works the same way as Popover hideDetached. It is enabled by default: the tooltip is now hidden when its target element is removed from the DOM, hidden with display: none, or scrolled out of a container that clips it. Previously, the tooltip stayed in place, floating over unrelated content. Set hideDetached={false} to restore the previous behavior. The prop has no effect on Tooltip.Floating, which is positioned relative to the mouse pointer.
Note that jsdom reports zero-size rectangles for every element, so in Jest and Vitest every tooltip is treated as detached and hidden unless the test wrapper sets env="test" on MantineProvider (as described in the Jest and Vitest guides) or the component is rendered with hideDetached={false}.
import { Box, Button, Group, Tooltip } from '@mantine/core';
function Demo() {
return (
<Box
bd="1px solid var(--mantine-color-dimmed)"
p="xl"
w={{ base: 340, sm: 400 }}
h={200}
style={{ overflow: 'auto' }}
>
<Box w={1000} h={400}>
<Group>
<Tooltip label="Hidden when detached" position="bottom" opened>
<Button>Hides when detached</Button>
</Tooltip>
<Tooltip label="Visible when detached" position="bottom" opened hideDetached={false}>
<Button>Stays visible</Button>
</Tooltip>
</Group>
</Box>
</Box>
);
}
Notifications now support withAutoCloseProgress prop. When set, a progress line that fills up until the notification auto closes is displayed at the bottom of every notification. The line fades out while the auto close timer is paused (for example, when the notification is hovered), starts over when the timer restarts, and uses the notification color. The prop sets the default for all notifications, it can be overridden for individual notifications with withAutoCloseProgress property in notifications.show and notifications.update functions:
import { Button, Group } from '@mantine/core';
import { notifications } from '@mantine/notifications';
function Demo() {
return (
<Group justify="center">
<Button
onClick={() =>
notifications.show({
title: 'Auto close progress',
message: 'This notification will close in 5 seconds',
withAutoCloseProgress: true,
autoClose: 5000,
})
}
>
Show notification with progress
</Button>
<Button
color="red"
onClick={() =>
notifications.show({
title: 'Something went wrong',
message: 'Progress line uses notification color',
color: 'red',
withAutoCloseProgress: true,
autoClose: 8000,
})
}
>
Red notification with progress
</Button>
</Group>
);
}
New notifications.promise function displays a loading notification while a promise is pending and updates it with success or error state once the promise settles. success and error can be functions that receive the resolved value or the rejection reason:
import { Button, Group } from '@mantine/core';
import { notifications } from '@mantine/notifications';
function saveDocument(shouldFail: boolean) {
return new Promise<{ name: string }>((resolve, reject) => {
setTimeout(() => {
if (shouldFail) {
reject(new Error('Network error'));
} else {
resolve({ name: 'report.pdf' });
}
}, 2000);
});
}
function Demo() {
const save = (shouldFail: boolean) =>
notifications.promise(saveDocument(shouldFail), {
loading: {
title: 'Saving document',
message: 'Please wait, it will take a couple of seconds',
},
success: (value) => ({
title: 'Document saved',
message: `${value.name} was saved successfully`,
}),
error: (error) => ({
title: 'Failed to save document',
message: (error as Error).message,
}),
});
return (
<Group justify="center">
<Button onClick={() => save(false)}>Save document</Button>
<Button color="red" onClick={() => save(true)}>
Save document (fails)
</Button>
</Group>
);
}
AppShell now supports resizing AppShell.Navbar/AppShell.Aside horizontally and AppShell.Header/AppShell.Footer vertically. Pass a useAppShellResize hook instance to the resize prop to enable it for the configured sections – handles support mouse, touch and keyboard, and can report drag-to-collapse. Each section accepts a label option to localize the aria-label of its handle. See AppShell examples for more details.
Note that when the resize prop is used, --app-shell-* CSS variables are defined on the AppShell root element instead of :root, so they cannot be read from content rendered in a Portal, for example from a Modal or a Drawer.
- New mantine-tanstack-start-template and TanStack Start guide to set up Mantine in a TanStack Start application.
- vite-template now uses Vite+: Vite, Vitest, oxlint and oxfmt run through the
vpCLI and are configured invite.config.mjs. - New StyleX guide explains how to style Mantine components with StyleX in a Vite application.
- HoverCard now opens on keyboard focus, closes with
Escapeor a press outside, and is announced by screen readers. Newevents,interactive,roleandreturnFocusprops, andonDismisscallback. - HoverCard no longer opens with a tap on touch devices. Set
events={{ focus: false, touch: true }}andcloseOnEscape={false}to restore the previous behavior. - Checkbox and Radio
variant="light"colors are resolved withtheme.variantColorResolver, so any CSS color or theme color with a shade can be used. - ActionBar with
keepMountednow uses ReactActivityinstead ofdisplay: none, so effects are paused while the bar is closed. SettransitionProps={{ keepMountedMode: 'display-none' }}to restore the previous behavior. - Mantine skills for AI coding agents (
mantine-form,mantine-combobox,mantine-custom-components) have been updated for 9.x with corrected API details and new patterns. - Gatsby and Redwood guides have been removed,
gatsby-templateandredwood-templateare no longer maintained. Existing applications can keep using Mantine, the setup does not change.
9.6.3
-
[@mantine/hooks]use-click-outside: Add capture phase support (#9213) -
[@mantine/core]Select: Fix dropdown not closing on blur when searchable is not set (#9215) -
[@mantine/core]PasswordInput: Fix aria-describedby not being taken from InputWrapperContext (#9216) -
[@mantine/core]Fix aria-labelledby referencing a missing label element in Checkbox.Group, Radio.Group, Switch.Group (#9217) -
[@mantine/core]Slider: Fix thumbProps not being passed to the thumb element (#9218) -
[@mantine/core]Table: Fix memoized rows rerendering when Table rerenders with the same props (#6422) -
[@mantine/hooks]use-intersection: Use the last entry from a batched observer callback (#9019) -
[@mantine/hooks]use-media-query: Catch matchMedia errors when reading the initial value synchronously (#9020) -
[@mantine/core]Portal: Cache shared portal node lookup (#9101) -
[@mantine/schedule]MobileMonthView: Fix multi-day events not showing when they start in the previous month (#9153) -
[@mantine/form]Fix removeListItem not clearing non-nested item errors (#9180) -
[@mantine/core]Rating: Fix value being changed by scroll gestures on touch devices (#9159) -
[@mantine/notifications]Fix uneven spacing in expanded stacks (#9176) -
[@mantine/charts]FixtextColorandgridColorprops being passed as attributes to the DOM node (#9181) -
[@mantine/hooks]use-hotkeys: Fix preventDefault not being applied when other hotkey options are set (#9164) -
[@mantine/hooks]use-throttled-callback: Fix callback becoming unresponsive after clearTimeout (#9146) -
[@mantine/hooks]use-roving-index: Fix disabled items not being skipped by ArrowLeft/ArrowRight in grid mode (#9169) -
[@mantine/hooks]use-mask: Fix transform not being applied to the initial input value (#9170)
9.6.2
-
[@mantine/core]Combobox: Fix incorrectaria-selectedsetting on up/down arrows press (#9205) -
[@mantine/core]NumberInput: Fixminandmaxboundaries not being respected whentrimLeadingZeroesOnBluris false (#9192) -
[@mantine/hooks]use-mask: Fix incorrect handling of input with mixed static values (#9196) -
[@mantine/schedule]Add option to resize bacground events (#9190) -
[@mantine/schedule]MobileMonthView: Fix missing localization for all day events label (#9191) -
[@mantine/hooks]use-scroll-spy: Fix stale nodes being used when element cannot be resolved by the given selector -
[@mantine/core]ComboboxPopover: Fix incorrect focus management -
[@mantine/charts]GaugeChart: Fix incorrectroundCapshandling with multiple sections (#9189) -
[@mantine/core]NumberInput: Fix incorrect thousands separator handling on paste (#9102)
9.6.1
-
[@mantine/ligtbox]Add option to render custom thumbnails for video -
[@mantine/core]OverflowList: Fix ResizeObserver console warning (#9177) -
[@mantine/core]Fix incorrect escape handling in Modal and Drawer stacks (#9188) -
[@mantine/core]SegmentedControl: Fix indicator disappearing when data list is replaced with a list with the same length (#9175) -
[@mantine/lightbox]Fix circular esm dependency (#9166) -
[@mantine/core]Accordion: Fix incorrect border radius being applied to the contained items -
[@mantine/schedule]Add event overlap mode support to WeekView and DayView -
[@mantine/core]Menu: Fix incorrectwithinPortalprop being available -
[@mantine/core]Popover: Fix position not being updated when prop changes when the dropdown is opened (#9156) -
[@mantine/schedule]Fix same-day events ending at exclusive midnight being dropped in WeekView and DayView components (#9157) -
[@mantine/hooks]use-interval: Fix timer restarting when fn changes (#9158) -
[@mantine/core]Textarea: Fix ResizeObserver loop error when autosize textarea width changes (#9162) -
[@mantine/hooks]use-collapse: Fix incorrect transition state switching when used with Activity (#9160)
9.6.0
View changelog with demos on mantine.dev website
You can now sponsor Mantine development with OpenCollective. All funds are used to improve Mantine and create new features and components.
New @mantine/lightbox package – a full-screen media lightbox with carousel navigation, zoom, thumbnails, toolbar customization, and store-based API. Supports image, video, and custom slides:
import '@mantine/lightbox/styles.css';
import { useState } from 'react';
import { Image, SimpleGrid } from '@mantine/core';
import { Lightbox, LightboxSlideData } from '@mantine/lightbox';
const images = [
'https://raw.githubusercontent.com/mantinedev/mantine/master/.demo/images/bg-1.png',
'https://raw.githubusercontent.com/mantinedev/mantine/master/.demo/images/bg-2.png',
'https://raw.githubusercontent.com/mantinedev/mantine/master/.demo/images/bg-3.png',
'https://raw.githubusercontent.com/mantinedev/mantine/master/.demo/images/bg-4.png',
'https://raw.githubusercontent.com/mantinedev/mantine/master/.demo/images/bg-5.png',
];
const slides: LightboxSlideData[] = images.map((src) => ({ src }));
function Demo() {
const [opened, setOpened] = useState(false);
const [index, setIndex] = useState(0);
return (
<>
<Lightbox
opened={opened}
onClose={() => setOpened(false)}
slides={slides}
currentIndex={index}
onIndexChange={setIndex}
/>
<SimpleGrid cols={3}>
{images.map((src, i) => (
<Image
key={src}
src={src}
radius="md"
style={{ cursor: 'pointer' }}
onClick={() => {
setIndex(i);
setOpened(true);
}}
/>
))}
</SimpleGrid>
</>
);
}
Key features:
- Zoom – click to zoom on desktop, double-tap on mobile, scroll wheel and pinch gestures
- Thumbnails – bottom thumbnail strip with active indicator
- Store API – mount once, open from anywhere (same pattern as Spotlight and Notifications)
- Video slides – native video player with auto-pause on navigation
- Custom slides – render anything with custom thumbnails
- Transitions – animated open and close with configurable
transitionProps(same API as Modal) - Keyboard shortcuts – Escape, arrows, F/T/Z for fullscreen/thumbnails/zoom
- Localization – every string is defined in the
labelsprop
Notifications now support renderNotification prop that allows you to completely replace the default notification with custom content. All animations (enter, exit, drag dismiss) are preserved for custom notifications:
import { Avatar, Button, Group, rem, Text } from '@mantine/core';
import { notifications } from '@mantine/notifications';
function Demo() {
return (
<Group justify="center">
<Button
onClick={() =>
notifications.show({
autoClose: false,
renderNotification: (notification) => (
<div
style={{
display: 'flex',
alignItems: 'center',
gap: rem(12),
padding: rem(16),
borderRadius: rem(8),
backgroundColor: 'var(--mantine-color-body)',
border: '1px solid var(--mantine-color-default-border)',
boxShadow: 'var(--mantine-shadow-lg)',
userSelect: 'none',
}}
>
<Avatar src={null} radius="xl" color="blue">
DM
</Avatar>
<div style={{ flex: 1, minWidth: 0 }}>
<Text size="sm" fw={600}>
Dan sent you a message
</Text>
<Text size="xs" c="dimmed" lineClamp={1}>
Hey, are you free for a quick call?
</Text>
<Group gap="xs" mt={8}>
<Button
size="compact-xs"
variant="filled"
onClick={() =>
notifications.hide(notification.id!)
}
>
Reply
</Button>
<Button
size="compact-xs"
variant="default"
onClick={() =>
notifications.hide(notification.id!)
}
>
Dismiss
</Button>
</Group>
</div>
</div>
),
message: '',
})
}
>
Show custom notification
</Button>
</Group>
);
}
Notifications now support layout="stacked" prop that displays notifications in a stacked layout where only the latest notification is fully visible, and older notifications peek out behind it:
import { Button, Group } from '@mantine/core';
import { Notifications, notifications } from '@mantine/notifications';
function Demo() {
return (
<>
{/* Replace your existing Notifications with layout="stacked" */}
<Notifications layout="stacked" />
<Group justify="center">
<Button
onClick={() => {
notifications.show({
title: 'New notification',
message: 'This notification is part of a stacked layout',
});
}}
>
Show stacked notification
</Button>
</Group>
</>
);
}
New ActionBar component – a fixed-position bottom bar for bulk selection actions. Designed to be controlled by table or checkbox selections, it provides a set of actions that can be performed on selected items.
import { useState } from 'react';
import { ActionBar, Button, Checkbox, Table, Text } from '@mantine/core';
const elements = [
{ position: 6, mass: 12.011, symbol: 'C', name: 'Carbon' },
{ position: 7, mass: 14.007, symbol: 'N', name: 'Nitrogen' },
{ position: 39, mass: 88.906, symbol: 'Y', name: 'Yttrium' },
{ position: 56, mass: 137.33, symbol: 'Ba', name: 'Barium' },
{ position: 58, mass: 140.12, symbol: 'Ce', name: 'Cerium' },
];
function Demo() {
const [selection, setSelection] = useState<number[]>([]);
const toggleRow = (position: number) =>
setSelection((current) =>
current.includes(position)
? current.filter((item) => item !== position)
: [...current, position]
);
const toggleAll = () =>
setSelection((current) =>
current.length === elements.length ? [] : elements.map((element) => element.position)
);
const rows = elements.map((element) => (
<Table.Tr
key={element.position}
bg={selection.includes(element.position) ? 'var(--mantine-color-blue-light)' : undefined}
>
<Table.Td>
<Checkbox
aria-label="Select row"
checked={selection.includes(element.position)}
onChange={() => toggleRow(element.position)}
/>
</Table.Td>
<Table.Td>{element.position}</Table.Td>
<Table.Td>{element.name}</Table.Td>
<Table.Td>{element.symbol}</Table.Td>
<Table.Td>{element.mass}</Table.Td>
</Table.Tr>
));
return (
<>
<Table>
<Table.Thead>
<Table.Tr>
<Table.Th>
<Checkbox
aria-label="Select all"
checked={selection.length === elements.length}
indeterminate={selection.length > 0 && selection.length !== elements.length}
onChange={toggleAll}
/>
</Table.Th>
<Table.Th>Element position</Table.Th>
<Table.Th>Element name</Table.Th>
<Table.Th>Symbol</Table.Th>
<Table.Th>Atomic mass</Table.Th>
</Table.Tr>
</Table.Thead>
<Table.Tbody>{rows}</Table.Tbody>
</Table>
<ActionBar opened={selection.length > 0} onClose={() => setSelection([])} shadow="md">
<Text size="sm">{selection.length} selected</Text>
<ActionBar.Divider />
<Button variant="default" size="compact-sm">
Delete
</Button>
<Button variant="default" size="compact-sm">
Move
</Button>
<Button variant="default" size="compact-sm">
Archive
</Button>
<ActionBar.CloseButton />
</ActionBar>
</>
);
}
RichTextEditor now includes a set of controls for editing tables. Install and register the Tiptap table extension (TableKit), then add the controls to the toolbar. RichTextEditor.TableInsert opens a grid to pick the table size, and the other controls add/remove rows and columns, toggle header row/column and merge/split cells. All table controls are automatically disabled when the cursor is not inside a table:
import { TableKit } from '@tiptap/extension-table';
import { useEditor } from '@tiptap/react';
import StarterKit from '@tiptap/starter-kit';
import { RichTextEditor } from '@mantine/tiptap';
function Demo() {
const editor = useEditor({
extensions: [StarterKit, TableKit],
content: `
<table>
<tbody>
<tr><th><p>Framework</p></th><th><p>Language</p></th></tr>
<tr><td><p>Mantine</p></td><td><p>TypeScript</p></td></tr>
<tr><td><p>Tiptap</p></td><td><p>TypeScript</p></td></tr>
</tbody>
</table>
<p></p>
`,
});
return (
<RichTextEditor editor={editor}>
<RichTextEditor.Toolbar sticky>
<RichTextEditor.ControlsGroup>
<RichTextEditor.TableInsert />
<RichTextEditor.TableDelete />
</RichTextEditor.ControlsGroup>
<RichTextEditor.ControlsGroup>
<RichTextEditor.TableColumnBefore />
<RichTextEditor.TableColumnAfter />
<RichTextEditor.TableColumnDelete />
</RichTextEditor.ControlsGroup>
<RichTextEditor.ControlsGroup>
<RichTextEditor.TableRowBefore />
<RichTextEditor.TableRowAfter />
<RichTextEditor.TableRowDelete />
</RichTextEditor.ControlsGroup>
<RichTextEditor.ControlsGroup>
<RichTextEditor.TableToggleHeaderRow />
<RichTextEditor.TableToggleHeaderColumn />
<RichTextEditor.TableMergeCells />
<RichTextEditor.TableSplitCell />
</RichTextEditor.ControlsGroup>
</RichTextEditor.Toolbar>
<RichTextEditor.Content />
</RichTextEditor>
);
}
RichTextEditor now supports collapsible sections. Install and register the Tiptap details extension (Details, DetailsSummary and DetailsContent), then add RichTextEditor.Details to the toolbar. The control wraps the current block in a collapsible details node, or removes it when the cursor is already inside one:
import { Details, DetailsSummary, DetailsContent } from '@tiptap/extension-details';
import { useEditor } from '@tiptap/react';
import StarterKit from '@tiptap/starter-kit';
import { RichTextEditor } from '@mantine/tiptap';
function Demo() {
const editor = useEditor({
extensions: [StarterKit, Details, DetailsSummary, DetailsContent],
content: `
<details>
<summary>Shipping and delivery</summary>
<p>Orders are processed within 1–2 business days and delivered in 3–5 business days.</p>
</details>
<details>
<summary>Returns and refunds</summary>
<p>You can return any item within 30 days of delivery for a full refund.</p>
</details>
<p></p>
`,
});
return (
<RichTextEditor editor={editor}>
<RichTextEditor.Toolbar sticky>
<RichTextEditor.ControlsGroup>
<RichTextEditor.Bold />
<RichTextEditor.Italic />
<RichTextEditor.Underline />
</RichTextEditor.ControlsGroup>
<RichTextEditor.ControlsGroup>
<RichTextEditor.Details />
</RichTextEditor.ControlsGroup>
</RichTextEditor.Toolbar>
<RichTextEditor.Content />
</RichTextEditor>
);
}
To support the control, Typography now styles details and summary elements – a border, padding and a custom disclosure triangle. This applies to all details elements inside Typography, not just those created by the editor. All of the new selectors have zero specificity (:where()), so they can be overridden without !important.
RichTextEditor can now display formatting marks. Install and register the Tiptap invisible characters extension, then add RichTextEditor.InvisibleCharacters to the toolbar. The control toggles the visibility of spaces, paragraph breaks and hard breaks, and reflects the current visibility as its active state:
import InvisibleCharacters from '@tiptap/extension-invisible-characters';
import { useEditor } from '@tiptap/react';
import StarterKit from '@tiptap/starter-kit';
import { RichTextEditor } from '@mantine/tiptap';
function Demo() {
const editor = useEditor({
extensions: [StarterKit, InvisibleCharacters.configure({ visible: false })],
content: `
<p>Toggle the control to reveal spaces and paragraph breaks.</p>
<p>Each space becomes a dot and every paragraph ends with a pilcrow.</p>
`,
});
return (
<RichTextEditor editor={editor}>
<RichTextEditor.Toolbar sticky>
<RichTextEditor.ControlsGroup>
<RichTextEditor.Bold />
<RichTextEditor.Italic />
<RichTextEditor.Underline />
</RichTextEditor.ControlsGroup>
<RichTextEditor.ControlsGroup>
<RichTextEditor.InvisibleCharacters />
</RichTextEditor.ControlsGroup>
</RichTextEditor.Toolbar>
<RichTextEditor.Content />
</RichTextEditor>
);
}
New GaugeChart component – a radial gauge chart for KPI and status display. Supports threshold sections, target marker, custom labels, and configurable arc angles.
import { GaugeChart } from '@mantine/charts';
function Demo() {
return <GaugeChart value={72} size={200} thickness={12} />;
}
New WaffleChart component – a part-to-whole grid chart with colored cells. Simpler and more compact alternative to pie/donut charts for displaying percentages and proportions.
// Demo.tsx
import { WaffleChart } from '@mantine/charts';
import { data } from './data';
function Demo() {
return <WaffleChart data={data} />;
}
// data.ts
import { WaffleChartCell } from '@mantine/charts';
export const data: WaffleChartCell[] = [
{ name: 'Chrome', value: 65, color: 'blue' },
{ name: 'Safari', value: 19, color: 'teal' },
{ name: 'Firefox', value: 10, color: 'orange' },
{ name: 'Other', value: 6, color: 'gray' },
];
New MatrixChart component – a generic x/y heatmap with categorical axes. Each cell is colored based on a value, useful for visualizing patterns in two-dimensional categorical data.
// Demo.tsx
import { MatrixChart } from '@mantine/charts';
import { data } from './data';
function Demo() {
return (
<MatrixChart
data={data}
yLabels={['James', 'Mary', 'Robert', 'Linda', 'Michael', 'Sarah', 'David', 'Emma']}
withYLabels
withTooltip
getTooltipLabel={({ x, y, value }) =>
`${y}, Mar ${x}: ${value === null ? 'No contributions' : `${value} contribution${value > 1 ? 's' : ''}`}`
}
/>
);
}
// data.ts
import { MatrixChartCell } from '@mantine/charts';
export const data: MatrixChartCell[] = [
{ x: '1', y: 'James', value: 7 },
{ x: '2', y: 'James', value: 10 },
{ x: '3', y: 'James', value: 2 },
{ x: '4', y: 'James', value: 10 },
{ x: '5', y: 'James', value: 8 },
{ x: '6', y: 'James', value: null },
{ x: '7', y: 'James', value: null },
{ x: '8', y: 'James', value: 6 },
{ x: '9', y: 'James', value: 2 },
{ x: '10', y: 'James', value: 8 },
{ x: '11', y: 'James', value: 1 },
{ x: '12', y: 'James', value: 3 },
{ x: '13', y: 'James', value: 7 },
{ x: '14', y: 'James', value: null },
{ x: '15', y: 'James', value: 9 },
{ x: '16', y: 'James', value: 10 },
{ x: '17', y: 'James', value: null },
{ x: '18', y: 'James', value: 1 },
{ x: '19', y: 'James', value: 8 },
{ x: '20', y: 'James', value: null },
{ x: '21', y: 'James', value: null },
{ x: '22', y: 'James', value: 5 },
{ x: '23', y: 'James', value: 8 },
{ x: '24', y: 'James', value: 2 },
{ x: '25', y: 'James', value: 5 },
{ x: '26', y: 'James', value: 6 },
{ x: '27', y: 'James', value: null },
{ x: '28', y: 'James', value: null },
{ x: '29', y: 'James', value: 7 },
{ x: '30', y: 'James', value: 7 },
{ x: '31', y: 'James', value: 6 },
{ x: '1', y: 'Mary', value: 3 },
{ x: '2', y: 'Mary', value: 1 },
// ... remaining data
];
New CandlestickChart component – a financial OHLC chart that displays open, high, low and close values as candles. Candles are colored based on their direction, the wick shows the high–low range and the body shows the open–close range. Supports custom colors, data keys, reference lines, axis labels, tooltip labels and value formatting.
// Demo.tsx
import { CandlestickChart } from '@mantine/charts';
import { data } from './data';
function Demo() {
return <CandlestickChart h={300} data={data} dataKey="date" tickLine="y" gridAxis="x" withXAxis={true} withYAxis={true} withTooltip={true} />;
}
// data.ts
export const data = [
{ date: 'Mar 01', open: 136, high: 142, low: 133, close: 140 },
{ date: 'Mar 02', open: 140, high: 145, low: 138, close: 139 },
{ date: 'Mar 03', open: 139, high: 141, low: 129, close: 131 },
{ date: 'Mar 04', open: 131, high: 134, low: 124, close: 125 },
{ date: 'Mar 05', open: 125, high: 133, low: 124, close: 132 },
{ date: 'Mar 06', open: 132, high: 138, low: 131, close: 137 },
{ date: 'Mar 07', open: 137, high: 137, low: 128, close: 129 },
{ date: 'Mar 08', open: 129, high: 135, low: 127, close: 134 },
{ date: 'Mar 09', open: 134, high: 148, low: 133, close: 146 },
{ date: 'Mar 10', open: 146, high: 152, low: 144, close: 151 },
{ date: 'Mar 11', open: 151, high: 154, low: 143, close: 145 },
{ date: 'Mar 12', open: 145, high: 149, low: 142, close: 148 },
{ date: 'Mar 13', open: 148, high: 156, low: 147, close: 155 },
{ date: 'Mar 14', open: 155, high: 158, low: 150, close: 152 },
{ date: 'Mar 15', open: 152, high: 153, low: 141, close: 143 },
{ date: 'Mar 16', open: 143, high: 147, low: 139, close: 146 },
{ date: 'Mar 17', open: 146, high: 160, low: 145, close: 159 },
{ date: 'Mar 18', open: 159, high: 164, low: 156, close: 157 },
{ date: 'Mar 19', open: 157, high: 162, low: 153, close: 161 },
{ date: 'Mar 20', open: 161, high: 168, low: 160, close: 166 },
];
AreaChart, BarChart, LineChart, CompositeChart and ScatterChart now support the referenceAreas prop that highlights a rectangular region of the plot – a weekend band, a target range, a threshold zone and similar annotations. Each area is bounded by x1/x2 and/or y1/y2 data values (omit one pair to span the full opposite axis) and supports a theme color and a label.
// Demo.tsx
import { AreaChart } from '@mantine/charts';
import { data } from './data';
function Demo() {
return (
<AreaChart
h={300}
data={data}
dataKey="date"
type="stacked"
series={[
{ name: 'Apples', color: 'indigo.6' },
{ name: 'Oranges', color: 'blue.6' },
{ name: 'Tomatoes', color: 'teal.6' },
]}
referenceAreas={[
{ x1: 'Mar 23', x2: 'Mar 25', color: 'red.6', label: 'Weekend' },
]}
/>
);
}
// data.ts
export const data = [
{
date: 'Mar 22',
Apples: 2890,
Oranges: 2338,
Tomatoes: 2452,
},
{
date: 'Mar 23',
Apples: 2756,
Oranges: 2103,
Tomatoes: 2402,
},
{
date: 'Mar 24',
Apples: 3322,
Oranges: 986,
Tomatoes: 1821,
},
{
date: 'Mar 25',
Apples: 3470,
Oranges: 2108,
Tomatoes: 2809,
},
{
date: 'Mar 26',
Apples: 3129,
Oranges: 1726,
Tomatoes: 2290,
},
];
AreaChart, BarChart, LineChart, CompositeChart and ScatterChart now support the referenceDots prop that marks individual points on the plot – a peak, an event, a record value or an anomaly. Each dot is positioned by x/y data coordinates and supports a radius, a theme color and a label. Reference dots are rendered on top of the chart series.
// Demo.tsx
import { AreaChart } from '@mantine/charts';
import { data } from './data';
function Demo() {
return (
<AreaChart
h={300}
data={data}
dataKey="date"
series={[
{ name: 'Apples', color: 'indigo.6' },
{ name: 'Oranges', color: 'blue.6' },
{ name: 'Tomatoes', color: 'teal.6' },
]}
referenceDots={[
{ x: 'Mar 25', y: 3470, color: 'red.6', label: 'Peak' },
]}
/>
);
}
// data.ts
export const data = [
{
date: 'Mar 22',
Apples: 2890,
Oranges: 2338,
Tomatoes: 2452,
},
{
date: 'Mar 23',
Apples: 2756,
Oranges: 2103,
Tomatoes: 2402,
},
{
date: 'Mar 24',
Apples: 3322,
Oranges: 986,
Tomatoes: 1821,
},
{
date: 'Mar 25',
Apples: 3470,
Oranges: 2108,
Tomatoes: 2809,
},
{
date: 'Mar 26',
Apples: 3129,
Oranges: 1726,
Tomatoes: 2290,
},
];
Note that referenceLines in AreaChart are now rendered on top of the areas instead of behind them, which makes them consistent with BarChart, LineChart, CompositeChart and ScatterChart, where reference lines were already painted over the series.
AreaChart now supports type="stream" that renders a streamgraph (also known as ThemeRiver) – a stacked area chart whose baseline flows around a central axis instead of being fixed to zero, producing the characteristic organic "river" shape. The y-axis is hidden by default for this type since its floating baseline makes the values not meaningful to read off:
// Demo.tsx
import { AreaChart } from '@mantine/charts';
import { data } from './data';
function Demo() {
return (
<AreaChart
h={300}
data={data}
dataKey="month"
type="stream"
series={[
{ name: 'Apples', color: 'indigo.6' },
{ name: 'Oranges', color: 'blue.6' },
{ name: 'Tomatoes', color: 'teal.6' },
{ name: 'Grapes', color: 'grape.6' },
]}
/>
);
}
// data.ts
export const data = [
{ month: 'Jan', Apples: 220, Oranges: 140, Tomatoes: 90, Grapes: 60 },
{ month: 'Feb', Apples: 260, Oranges: 180, Tomatoes: 120, Grapes: 90 },
{ month: 'Mar', Apples: 300, Oranges: 240, Tomatoes: 180, Grapes: 140 },
{ month: 'Apr', Apples: 340, Oranges: 320, Tomatoes: 260, Grapes: 200 },
{ month: 'May', Apples: 380, Oranges: 420, Tomatoes: 360, Grapes: 280 },
{ month: 'Jun', Apples: 420, Oranges: 520, Tomatoes: 460, Grapes: 360 },
{ month: 'Jul', Apples: 400, Oranges: 560, Tomatoes: 520, Grapes: 420 },
{ month: 'Aug', Apples: 360, Oranges: 520, Tomatoes: 560, Grapes: 460 },
{ month: 'Sep', Apples: 300, Oranges: 440, Tomatoes: 520, Grapes: 420 },
{ month: 'Oct', Apples: 260, Oranges: 340, Tomatoes: 440, Grapes: 360 },
{ month: 'Nov', Apples: 220, Oranges: 260, Tomatoes: 340, Grapes: 280 },
{ month: 'Dec', Apples: 200, Oranges: 200, Tomatoes: 260, Grapes: 200 },
];
ScatterChart now supports the withRightYAxis prop that displays an additional Y axis on the right side of the chart, configurable with rightYAxisProps and rightYAxisLabel. Bind data series to the right Y axis by setting yAxisId: 'right' in the data object – series without yAxisId are bound to the left Y axis. Both axes use the same dataKey.y value, but their scales are calculated independently from the series assigned to them:
// Demo.tsx
import { ScatterChart } from '@mantine/charts';
import { data } from './data';
function Demo() {
return (
<ScatterChart
h={350}
data={data}
dataKey={{ x: 'month', y: 'value' }}
withLegend
withRightYAxis
xAxisLabel="Month"
yAxisLabel="Revenue"
rightYAxisLabel="Conversion rate"
rightYAxisProps={{ unit: '%' }}
/>
);
}
// data.ts
export const data = [
{
color: 'indigo.6',
name: 'Revenue',
data: [
{ month: 1, value: 1200 },
{ month: 2, value: 1400 },
{ month: 3, value: 1350 },
{ month: 4, value: 1800 },
{ month: 5, value: 2100 },
{ month: 6, value: 1950 },
{ month: 7, value: 2400 },
{ month: 8, value: 2650 },
{ month: 9, value: 2300 },
{ month: 10, value: 2800 },
{ month: 11, value: 3100 },
{ month: 12, value: 3400 },
],
},
{
color: 'teal.6',
name: 'Conversion rate',
yAxisId: 'right',
data: [
{ month: 1, value: 3.4 },
{ month: 2, value: 3.9 },
{ month: 3, value: 3.1 },
{ month: 4, value: 4.2 },
{ month: 5, value: 4.8 },
{ month: 6, value: 4.1 },
{ month: 7, value: 5.3 },
{ month: 8, value: 5.9 },
{ month: 9, value: 5.1 },
{ month: 10, value: 6.2 },
{ month: 11, value: 6.8 },
{ month: 12, value: 7.4 },
],
},
];
Stepper component now supports the labelPosition prop. Set labelPosition="bottom" to display the step label and description below the step icon:
import { useState } from 'react';
import { Stepper } from '@mantine/core';
function Demo() {
const [active, setActive] = useState(1);
return (
<Stepper active={active} onStepClick={setActive} labelPosition="bottom">
<Stepper.Step label="Account" />
<Stepper.Step label="Verification" />
<Stepper.Step label="Access" />
</Stepper>
);
}
Cascader with expandTrigger="hover" now keeps the open column in place while the cursor moves diagonally toward it – options that the cursor passes over on the way no longer replace it. Set safeAreaPolygon={false} to expand on every hover immediately, or pass an object to configure Floating UI safePolygon options:
import { Cascader, useMatches } from '@mantine/core';
import { data } from './data';
function Demo() {
const withColumns = useMatches({ base: false, sm: true });
return (
<Cascader
withColumns={withColumns}
expandTrigger="hover"
safeAreaPolygon={false}
label="Location"
placeholder="Hover to expand"
data={data}
/>
);
}
YearView now supports the renderDay prop that replaces the entire content of a day cell. The function is called with the day date in YYYY-MM-DD format and the events grouped on that day – the same list that is used to render the default indicators, but without the three items limit. This makes it possible to display counts, badges or icons instead of the default dots:
// Demo.tsx
import dayjs from 'dayjs';
import { YearView } from '@mantine/schedule';
import { events } from './data';
function Demo() {
return (
<YearView
date={new Date()}
events={events}
renderDay={(date, dayEvents) => (
<>
{dayjs(date).date()}
{dayEvents.length > 0 && (
<div
style={{
position: 'absolute',
bottom: 0,
insetInlineEnd: 0,
minWidth: 12,
height: 12,
borderRadius: 12,
fontSize: 9,
lineHeight: '12px',
fontWeight: 700,
textAlign: 'center',
color: 'var(--mantine-color-white)',
backgroundColor: `var(--mantine-color-${dayEvents[0].color}-filled)`,
}}
>
{dayEvents.length}
</div>
)}
</>
)}
/>
);
}
ResourcesMonthView now supports the withEventResize prop. Events can be resized by dragging their start or end edges, and the onEventResize callback is called with the updated event start and end dates. Resizing snaps to whole days and preserves the event's original time of day. Use canResizeEvent to control which events can be resized:
// Demo.tsx
import dayjs from 'dayjs';
import { useState } from 'react';
import { ResourcesMonthView, ScheduleEventData } from '@mantine/schedule';
import { events as initialEvents, resources } from './data';
function Demo() {
const [date, setDate] = useState(dayjs().format('YYYY-MM-DD'));
const [events, setEvents] = useState<ScheduleEventData[]>(initialEvents);
return (
<ResourcesMonthView
date={date}
onDateChange={setDate}
resources={resources}
events={events}
withEventResize
onEventResize={({ eventId, newStart, newEnd }) => {
setEvents((current) =>
current.map((event) =>
event.id === eventId
? { ...event, start: newStart, end: newEnd }
: event
)
);
}}
startScrollDate={dayjs().format('YYYY-MM-DD')}
/>
);
}
// data.ts
import dayjs from 'dayjs';
import { ScheduleResourceData } from '@mantine/schedule';
const today = dayjs().format('YYYY-MM-DD');
const tomorrow = dayjs().add(1, 'day').format('YYYY-MM-DD');
const nextWeek = dayjs().add(5, 'day').format('YYYY-MM-DD');
const resources: ScheduleResourceData[] = [
{ id: 'tokyo', label: 'Meeting room: Tokyo' },
{ id: 'paris', label: 'Meeting room: Paris' },
{ id: 'new-york', label: 'Meeting room: New York' },
];
const events = [
{
id: 1,
title: 'Team Standup',
start: \`\${today} 09:00:00\`,
end: \`\${today} 09:30:00\`,
color: 'blue',
resourceId: 'tokyo',
},
{
id: 2,
title: 'Sprint Planning',
start: \`\${today} 10:00:00\`,
end: \`\${today} 11:30:00\`,
color: 'green',
resourceId: 'paris',
},
{
id: 3,
title: 'Design Review',
start: \`\${tomorrow} 13:00:00\`,
end: \`\${tomorrow} 14:00:00\`,
color: 'orange',
resourceId: 'tokyo',
},
{
id: 4,
title: 'Client Call',
start: \`\${tomorrow} 09:30:00\`,
end: \`\${tomorrow} 10:30:00\`,
color: 'violet',
resourceId: 'new-york',
},
{
id: 5,
title: 'Workshop',
start: \`\${nextWeek} 14:00:00\`,
end: \`\${nextWeek} 16:00:00\`,
color: 'pink',
resourceId: 'paris',
},
];
Time-grid Schedule views (DayView, WeekView, ResourcesDayView, ResourcesWeekView) now support eventDragInterval and eventResizeInterval props that set the snap step used when events are moved and resized, independent of the intervalMinutes grid size. For example, a 30-minute grid can allow 15-minute drag and resize increments. A ghost preview shows where the event will land while dragging:
import { useState } from 'react';
import dayjs from 'dayjs';
import { DayView, ScheduleEventData } from '@mantine/schedule';
const today = dayjs().format('YYYY-MM-DD');
const initialEvents: ScheduleEventData[] = [
{
id: 1,
title: 'Morning Standup',
start: `${today} 09:00:00`,
end: `${today} 09:30:00`,
color: 'blue',
},
{
id: 2,
title: 'Team Meeting',
start: `${today} 11:00:00`,
end: `${today} 12:00:00`,
color: 'green',
},
{
id: 3,
title: 'Code Review',
start: `${today} 14:00:00`,
end: `${today} 15:00:00`,
color: 'violet',
},
];
function Demo() {
const [events, setEvents] = useState(initialEvents);
const handleEventDrop = ({ eventId, newStart, newEnd }: { eventId: string | number; newStart: string; newEnd: string }) => {
setEvents((prev) =>
prev.map((event) =>
event.id === eventId ? { ...event, start: newStart, end: newEnd } : event
)
);
};
return (
<DayView
date={new Date()}
events={events}
startTime="08:00:00"
endTime="18:00:00"
intervalMinutes={30}
eventDragInterval={15}
withSubHourGridLines={false}
withEventsDragAndDrop
onEventDrop={handleEventDrop}
/>
);
}
import { useState } from 'react';
import dayjs from 'dayjs';
import { DayView, ScheduleEventData } from '@mantine/schedule';
const today = dayjs().format('YYYY-MM-DD');
const initialEvents: ScheduleEventData[] = [
{
id: 1,
title: 'Morning Standup',
start: `${today} 09:00:00`,
end: `${today} 09:30:00`,
color: 'blue',
},
{
id: 2,
title: 'Team Meeting',
start: `${today} 11:00:00`,
end: `${today} 12:00:00`,
color: 'green',
},
{
id: 3,
title: 'Code Review',
start: `${today} 14:00:00`,
end: `${today} 15:00:00`,
color: 'violet',
},
];
function Demo() {
const [events, setEvents] = useState(initialEvents);
const handleEventResize = ({ eventId, newStart, newEnd }: { eventId: string | number; newStart: string; newEnd: string }) => {
setEvents((prev) =>
prev.map((event) =>
event.id === eventId ? { ...event, start: newStart, end: newEnd } : event
)
);
};
return (
<DayView
date={new Date()}
events={events}
startTime="08:00:00"
endTime="18:00:00"
intervalMinutes={30}
eventResizeInterval={15}
withSubHourGridLines={false}
withEventResize
onEventResize={handleEventResize}
/>
);
}
Dropzone now depends on react-dropzone 20 (previously 15). The upgrade brings several behavior and type changes:
maxFilesno longer rejects the entire batch when more files are picked than the limit allows. Files up to the limit are now accepted and the rest are rejected. For example, picking 3 files withmaxFiles={2}callsonDropwith the first 2 files andonRejectwith the third – previously all 3 files were rejected andonDropwas called with an empty array.FileWithPathtype now has requiredpathandrelativePathproperties, they were optional before. The default file aggregator always sets both values, soonDropfiles can be read without optional chaining. If you provide a customgetFilesFromEventthat returns plainFileobjects, these properties are not set at runtime.getFilesFromEventprop now receivesDropEvent | FileSystemFileHandle[]instead ofDropEvent– the File System Access API path passes file handles to the aggregator. Update the parameter type of custom aggregators to accept both.react-dropzone20 requires Node.js 22 or later. Mantine now requires Node.js 22 as well – Node.js 20 reached end of life in April 2026. This affects your development environment only, browser support is not changed.
- ColorInput now supports
fullWidthprop: the dropdown matches the width of the input and the color picker inside it fills the available space. - FloatingWindow now supports
onSizeChange,onResizeStartandonResizeEndcallbacks that mirroronPositionChange,onDragStartandonDragEndused for dragging. Sizes passed toonSizeChangeare measured after the new size has been applied, so they are already clamped by thedimensionsand viewport constraints. - PasswordInput now supports
visibilityToggleFocusableprop that puts the visibility toggle in the tab order: the button receivestabindex="0"and can be activated with Enter or Space. - Schedule views (
DayView,WeekView,MonthView,ResourcesDayView,ResourcesWeekView) now supportwithInteractiveBackgroundEventsprop – background events (display: 'background') become clickable and triggeronEventClick, which makes it possible to open an edit modal for unavailability blocks and similar events. - use-scroll-spy hook
scrollHostoption now accepts a ref object in addition to a resolvedHTMLElement– the hook readsref.currentinternally once the element is mounted, so the scroll host does not need to exist on the first render. - YearView now supports
withWeekendDaysprop. SetwithWeekendDays={false}to hide weekend days – every month grid shrinks to the remaining columns and events that fall only on hidden days are not displayed.
9.5.2
-
[@mantine/hooks]use-debounced-value: Fixleading: truefiring multiple times per burst and emiting a stale value (#9119) -
[@mantine/schedule]Fix recurring events not working with timzones (#9112) -
[@mantine/dates]FixminDateused for default date in some cases (#9117) -
[@mantine/core]Tooltip: Fix tooltip setting NaN in top/left position style when event position values cannot be read (#9131) -
[@mantine/dates]TimePicker: Fix incorrect focus handling of partially filled hours field (#9128) -
[@mantine/core]RollingNumber: Fix incorrect copy event handling (#9132) -
[@mantine/core]Notification: Fix incorrectcloseButtonPropstype (#9134) -
[@mantine/code-highlight]Add support for lazy languages loading (#9141) -
[@mantine/code-highlight]CodeHighlight: Add prop to keep indentation of the first line of the code block (#9140) -
[@mantine/dates]Add missing formatting functions to MiniCalendarm DateInput and YarsList components -
[@mantine/schedule]WeekView: Improve performance of events positioning algorithm (#9075) -
[@mantine/form]Add new useWatchValue hook -
[@mantine/core]Fix Combobox-based components not working correctly with Chrome autocomplete
9.5.1
-
[@mantine/tiptap]Fix controls being initially disabledbefore element is focused -
[@mantine/tiptap]Fix source code control wrapping content with extra p tag -
[@mantine/hooks]use-scroll-spy: Allow usage with refs (#9025) -
[@mantine/core]ColorInput: Add support for fullWidth prop (#9061) -
[@mantine/core]Checkbox: Fix incottect indeterminate aria attributes handling in Checkbox.Card (#9095) -
[@mantine/core]FloatingIndicator: Fix position and size calculation under scaled ancestors (#9071) -
[@mantine/core]Tooltip: Add interactive prop support (#9072) -
[@mantine/core]Cascader: Add safe area polygon support -
[@mantine/core]PasswordInput: Add option to change whether the visibility toggle is focusable (#9090) -
[@mantine/charts]ScatterChart: Add option to add second y axis -
[@mantine/schedule]YearView: AddrenderDayprop support -
[@mantine/schedule]YearView: Add option to hide weekend days -
[@mantine/core]InputWrapper: Fixcomponent: divtriggering typescript error if passed todescriptionProps -
[@mantine/schedule]ResourcesMonthView: Add option to resize events -
[@mantine/core]FloatingWindow: Add support foronSizeChangeandonResizeStartprops (#9085)