Bump the dash-network group across 1 directory with 2 updates

[dependabot]

Updates the requirements on dash-mui-charts and dash-emoji-mart to permit the latest version.
Updates dash-mui-charts to 1.4.0

Release notes

Sourced from dash-mui-charts's releases.

v1.4.0

Boilerplate migration — M5 (API reference)

• NEW /api page: every prop of all 13 components as tables generated from the components' own metadata via the .. kwargs:: directive — they can never drift from the installed version. Enabling fix in lib/directives/kwargs.py: the numpy-style override (built for dash-mantine-components docstrings) shadowed markdown2dash's own parser for dash-generate-components docstrings, so dash-built components rendered EMPTY tables; the hook now falls back to the base parser when it sees "Keyword arguments:". Navbar gains a Reference section; route count 40 → 41 (both parity baselines re-recorded deliberately).
• Home stays the bespoke Python page it already was — it mounts no charts, carries the brand/install/catalog and a full LLMS_DOC, and per-satellite custom homes are the network norm. Changelog likewise stays a Python page (its disk read is exercised by the suite on every run).

Fixed — tree rendering under the boilerplate shell (owner review)

• TreeView and SimpleTreeView now follow the theme toggle — both components gained the data-mantine-color-scheme watcher + MUI ThemeProvider that TreeViewPro and TimeClock already had, so checkboxes, icons and edit fields switch with light/dark mode instead of rendering in the light palette everywhere (component fix in src/lib/components, bundle + wrappers rebuilt; wrappers regenerated on the current dash-generate-components, gaining its dash≤4.1 compat shim).
• Trees no longer overflow their fixed-height boxes — the boilerplate's global markdown list styling (ul/ol and li margins in assets/main.css) leaked into MUI's nested ul/li tree DOM, inflating every tree's height (a height=200 tree bled into the next section on /tree-icons). Neutralized inside tree roots via assets/dark-mode.css; upstream, the boilerplate rule should arguably be prose-scoped.
• The /tree-icons SX demo's hardcoded light #f8f9ff background became var(--mantine-color-default) — it was unreadable in dark mode.
• The height prop now actually contains the tree (TreeView and SimpleTreeView): a fixed height previously sized the wrapper only — block children grow past a fixed-height parent and divs don't clip, so the tree rendered full-length over the next section. height now implies overflow: auto on the wrapper, making the /tree-icons "Fixed Height with Scroll" demo do what its title says.

Boilerplate migration — M4 (TreeView + Date & Time Pickers)

• Ten more pages markdown-driven — the eight TreeView pages (basic, simple, selection, expansion, editing, icons, disabled, and the Pro page with its live license-posture badge kept) and both pickers (/time-clock, and /time-clock-lab with its liquid-glass styling intact). Whole-page transforms, ids and callbacks verbatim; the four

... (truncated)

Changelog

Sourced from dash-mui-charts's changelog.

[1.4.0] - 2026-08-03

Boilerplate migration — M5 (API reference)

• NEW /api page: every prop of all 13 components as tables generated from the components' own metadata via the .. kwargs:: directive — they can never drift from the installed version. Enabling fix in lib/directives/kwargs.py: the numpy-style override (built for dash-mantine-components docstrings) shadowed markdown2dash's own parser for dash-generate-components docstrings, so dash-built components rendered EMPTY tables; the hook now falls back to the base parser when it sees "Keyword arguments:". Navbar gains a Reference section; route count 40 → 41 (both parity baselines re-recorded deliberately).
• Home stays the bespoke Python page it already was — it mounts no charts, carries the brand/install/catalog and a full LLMS_DOC, and per-satellite custom homes are the network norm. Changelog likewise stays a Python page (its disk read is exercised by the suite on every run).

Fixed — tree rendering under the boilerplate shell (owner review)

• TreeView and SimpleTreeView now follow the theme toggle — both components gained the data-mantine-color-scheme watcher + MUI ThemeProvider that TreeViewPro and TimeClock already had, so checkboxes, icons and edit fields switch with light/dark mode instead of rendering in the light palette everywhere (component fix in src/lib/components, bundle + wrappers rebuilt; wrappers regenerated on the current dash-generate-components, gaining its dash≤4.1 compat shim).
• Trees no longer overflow their fixed-height boxes — the boilerplate's global markdown list styling (ul/ol and li margins in assets/main.css) leaked into MUI's nested ul/li tree DOM, inflating every tree's height (a height=200 tree bled into the next section on /tree-icons). Neutralized inside tree roots via assets/dark-mode.css; upstream, the boilerplate rule should arguably be prose-scoped.
• The /tree-icons SX demo's hardcoded light #f8f9ff background became var(--mantine-color-default) — it was unreadable in dark mode.
• The height prop now actually contains the tree (TreeView and SimpleTreeView): a fixed height previously sized the wrapper only — block children grow past a fixed-height parent and divs don't clip, so the tree rendered full-length over the next section. height now implies overflow: auto on the wrapper, making the /tree-icons "Fixed Height with Scroll" demo do what its title says.

Boilerplate migration — M4 (TreeView + Date & Time Pickers)

• Ten more pages markdown-driven — the eight TreeView pages (basic, simple, selection, expansion, editing, icons, disabled, and the Pro page with its live license-posture badge kept) and both pickers (/time-clock, and /time-clock-lab with its liquid-glass styling intact). Whole-page transforms, ids and callbacks verbatim; the four

... (truncated)

Commits

• See full diff in compare view

Updates dash-emoji-mart to 0.2.1

Release notes

Sourced from dash-emoji-mart's releases.

v0.2.1

Two things: a picker bug that made whole custom categories invisible, and this site joining the 2plot network properly. Only the first affects pip install dash-emoji-mart.

This is the first 0.2.x anyone can install. 0.2.0 below was written, dated and never shipped — no v0.2.0 tag was ever pushed and nothing was uploaded, so the newest thing pip install dash-emoji-mart has ever returned is still 0.0.3 from 2024. Read the two sections together: 0.2.0 is what changed in the repository, 0.2.1 is what changed since, and a single v0.2.1 tag publishes both at once.

Fixed — the component

• Custom emojis whose src is a dimensionless SVG rendered as nothing. emoji-mart sizes a custom emoji's image with max-width/max-height and nothing else. A raster source has intrinsic dimensions and scales down to fit; an SVG carrying only a viewBox has no intrinsic size, so width: auto under a bare max-width resolves to zero. The emoji was in the DOM, focusable and clickable — and 0×0.

  It looked arbitrary rather than systematic, because it depended only on what the author happened to link. Iconify's API SVGs ship width="1em" and were always fine; SVGs straight off a repo were not. On the docs site's own custom-emoji demo that meant one category rendered and the next two were blank strips under their headings.

  The component now adopts a stylesheet into the picker's shadow root giving custom-emoji images width: 1em; height: 1em; object-fit: contain. 1em is the size emoji-mart already intends — it sets font-size to emojiSize on each grid button and to the larger preview size in the footer — so one rule is right in both places, non-square artwork is not distorted, and raster sources render exactly as before.

• theme="auto" follows the APP, then the OS — in that order. emoji-mart's "auto" reads prefers-color-scheme and nothing else, which is the wrong signal in a Dash app: almost every one ships a theme toggle, and a toggle does not touch the OS. On a machine set to dark, flipping a Dash Mantine app to light left every picker dark against a white page — and it looked like the component ignoring its own theme prop.

  The component now prefers data-mantine-color-scheme on <html> when the document advertises one, and falls back to the media query otherwise. Reading an attribute adds no dependency on DMC: an app that does not set it behaves exactly as before. An explicit theme="light"/"dark" is still passed straight through, and the resolution re-runs on a toggle without a remount.

  This is why the docs site had the bug on six of its pages: only /theming wired the clientside callback its own prose recommends. That

... (truncated)

Changelog

Sourced from dash-emoji-mart's changelog.

[0.2.1] — 2026-08-01

Two things: a picker bug that made whole custom categories invisible, and this site joining the 2plot network properly. Only the first affects pip install dash-emoji-mart.

This is the first 0.2.x anyone can install. 0.2.0 below was written, dated and never shipped — no v0.2.0 tag was ever pushed and nothing was uploaded, so the newest thing pip install dash-emoji-mart has ever returned is still 0.0.3 from 2024. Read the two sections together: 0.2.0 is what changed in the repository, 0.2.1 is what changed since, and a single v0.2.1 tag publishes both at once.

Fixed — the component

• Custom emojis whose src is a dimensionless SVG rendered as nothing. emoji-mart sizes a custom emoji's image with max-width/max-height and nothing else. A raster source has intrinsic dimensions and scales down to fit; an SVG carrying only a viewBox has no intrinsic size, so width: auto under a bare max-width resolves to zero. The emoji was in the DOM, focusable and clickable — and 0×0.

  It looked arbitrary rather than systematic, because it depended only on what the author happened to link. Iconify's API SVGs ship width="1em" and were always fine; SVGs straight off a repo were not. On the docs site's own custom-emoji demo that meant one category rendered and the next two were blank strips under their headings.

  The component now adopts a stylesheet into the picker's shadow root giving custom-emoji images width: 1em; height: 1em; object-fit: contain. 1em is the size emoji-mart already intends — it sets font-size to emojiSize on each grid button and to the larger preview size in the footer — so one rule is right in both places, non-square artwork is not distorted, and raster sources render exactly as before.

• theme="auto" follows the APP, then the OS — in that order. emoji-mart's "auto" reads prefers-color-scheme and nothing else, which is the wrong signal in a Dash app: almost every one ships a theme toggle, and a toggle does not touch the OS. On a machine set to dark, flipping a Dash Mantine app to light left every picker dark against a white page — and it looked like the component ignoring its own theme prop.

  The component now prefers data-mantine-color-scheme on <html> when the document advertises one, and falls back to the media query otherwise. Reading an attribute adds no dependency on DMC: an app that does not set it behaves exactly as before. An explicit theme="light"/"dark" is still passed straight through, and the resolution re-runs on a toggle without a remount.

  This is why the docs site had the bug on six of its pages: only /theming wired the clientside callback its own prose recommends. That

... (truncated)

Commits

• See full diff in compare view