4164 Commits
Author SHA1 Message Date
zsviczian 2c3dcc06ec fix(editor): prevent frame-drag lag when selecting large groups (#12692)
fix: avoid repeatedly selecting the same group during frame dragging
2026-11-19 20:01:22 +01:00
Excalidraw Botanddwelle 091bc0e9d8 chore(editor): Update translations from Crowdin (#12070)
* New translations en.json (Latvian)

[ci skip]

* New translations en.json (Azerbaijani)

[ci skip]

* New translations en.json (Hindi)

[ci skip]

* New translations en.json (Burmese)

[ci skip]

* New translations en.json (Chinese Traditional, Hong Kong)

[ci skip]

* New translations en.json (Sinhala)

[ci skip]

* New translations en.json (Uzbek)

[ci skip]

* New translations en.json (Norwegian Bokmal)

[ci skip]

* New translations en.json (Occitan)

[ci skip]

* New translations en.json (German, Switzerland)

[ci skip]

* New translations en.json (Bengali, India)

[ci skip]

* New translations en.json (Kabyle)

[ci skip]

* New translations en.json (Karakalpak)

[ci skip]

* New translations en.json (Romanian)

[ci skip]

* New translations en.json (Norwegian Nynorsk)

[ci skip]

* New translations en.json (Norwegian Bokmal)

[ci skip]

* New translations en.json (German)

[ci skip]

* New translations en.json (German)

[ci skip]

* New translations en.json (Japanese)

[ci skip]

* New translations en.json (Danish)

[ci skip]

* New translations en.json (Dutch)

[ci skip]

* New translations en.json (Danish)

[ci skip]

* New translations en.json (Dutch)

[ci skip]

* New translations en.json (Dutch)

[ci skip]

* New translations en.json (Dutch)

[ci skip]

* New translations en.json (German)

[ci skip]

* New translations en.json (Indonesian)

[ci skip]

* New translations en.json (Romanian)

[ci skip]

* New translations en.json (French)

[ci skip]

* New translations en.json (Spanish)

[ci skip]

* New translations en.json (Danish)

[ci skip]

* New translations en.json (German)

[ci skip]

* New translations en.json (Basque)

[ci skip]

* New translations en.json (Hebrew)

[ci skip]

* New translations en.json (Italian)

[ci skip]

* New translations en.json (Japanese)

[ci skip]

* New translations en.json (Korean)

[ci skip]

* New translations en.json (Dutch)

[ci skip]

* New translations en.json (Polish)

[ci skip]

* New translations en.json (Portuguese)

[ci skip]

* New translations en.json (Russian)

[ci skip]

* New translations en.json (Slovak)

[ci skip]

* New translations en.json (Slovenian)

[ci skip]

* New translations en.json (Swedish)

[ci skip]

* New translations en.json (Turkish)

[ci skip]

* New translations en.json (Ukrainian)

[ci skip]

* New translations en.json (Chinese Simplified)

[ci skip]

* New translations en.json (Chinese Traditional)

[ci skip]

* New translations en.json (Portuguese, Brazilian)

[ci skip]

* New translations en.json (Norwegian Nynorsk)

[ci skip]

* New translations en.json (Norwegian Bokmal)

[ci skip]

* New translations en.json (German, Switzerland)

[ci skip]

* New translations en.json (Romanian)

[ci skip]

* New translations en.json (Dutch)

[ci skip]

* New translations en.json (German)

[ci skip]

* New translations en.json (Russian)

[ci skip]

* New translations en.json (Danish)

[ci skip]

* New translations en.json (Chinese Traditional)

[ci skip]

* New translations en.json (Indonesian)

[ci skip]

* New translations en.json (Thai)

[ci skip]

* New translations en.json (Romanian)

[ci skip]

* New translations en.json (French)

[ci skip]

* New translations en.json (Spanish)

[ci skip]

* New translations en.json (Arabic)

[ci skip]

* New translations en.json (Bulgarian)

[ci skip]

* New translations en.json (Catalan)

[ci skip]

* New translations en.json (Czech)

[ci skip]

* New translations en.json (Danish)

[ci skip]

* New translations en.json (German)

[ci skip]

* New translations en.json (Greek)

[ci skip]

* New translations en.json (Basque)

[ci skip]

* New translations en.json (Finnish)

[ci skip]

* New translations en.json (Hebrew)

[ci skip]

* New translations en.json (Hungarian)

[ci skip]

* New translations en.json (Italian)

[ci skip]

* New translations en.json (Japanese)

[ci skip]

* New translations en.json (Korean)

[ci skip]

* New translations en.json (Kurdish)

[ci skip]

* New translations en.json (Lithuanian)

[ci skip]

* New translations en.json (Dutch)

[ci skip]

* New translations en.json (Punjabi)

[ci skip]

* New translations en.json (Polish)

[ci skip]

* New translations en.json (Portuguese)

[ci skip]

* New translations en.json (Russian)

[ci skip]

* New translations en.json (Slovak)

[ci skip]

* New translations en.json (Slovenian)

[ci skip]

* New translations en.json (Swedish)

[ci skip]

* New translations en.json (Turkish)

[ci skip]

* New translations en.json (Ukrainian)

[ci skip]

* New translations en.json (Chinese Simplified)

[ci skip]

* New translations en.json (Chinese Traditional)

[ci skip]

* New translations en.json (Vietnamese)

[ci skip]

* New translations en.json (Galician)

[ci skip]

* New translations en.json (Portuguese, Brazilian)

[ci skip]

* New translations en.json (Persian)

[ci skip]

* New translations en.json (Khmer)

[ci skip]

* New translations en.json (Tamil)

[ci skip]

* New translations en.json (Bengali)

[ci skip]

* New translations en.json (Marathi)

[ci skip]

* New translations en.json (Norwegian Nynorsk)

[ci skip]

* New translations en.json (Kazakh)

[ci skip]

* New translations en.json (Latvian)

[ci skip]

* New translations en.json (Azerbaijani)

[ci skip]

* New translations en.json (Hindi)

[ci skip]

* New translations en.json (Burmese)

[ci skip]

* New translations en.json (Chinese Traditional, Hong Kong)

[ci skip]

* New translations en.json (Sinhala)

[ci skip]

* New translations en.json (Uzbek)

[ci skip]

* New translations en.json (Norwegian Bokmal)

[ci skip]

* New translations en.json (Occitan)

[ci skip]

* New translations en.json (German, Switzerland)

[ci skip]

* New translations en.json (Bengali, India)

[ci skip]

* New translations en.json (Kabyle)

[ci skip]

* New translations en.json (Karakalpak)

[ci skip]

* New translations en.json (Romanian)

[ci skip]

* New translations en.json (Romanian)

[ci skip]

* New translations en.json (Dutch)

[ci skip]

* New translations en.json (Thai)

[ci skip]

* New translations en.json (Russian)

[ci skip]

* New translations en.json (Indonesian)

[ci skip]

* New translations en.json (Thai)

[ci skip]

* New translations en.json (Romanian)

[ci skip]

* New translations en.json (French)

[ci skip]

* New translations en.json (Spanish)

[ci skip]

* New translations en.json (Arabic)

[ci skip]

* New translations en.json (Bulgarian)

[ci skip]

* New translations en.json (Catalan)

[ci skip]

* New translations en.json (Czech)

[ci skip]

* New translations en.json (Danish)

[ci skip]

* New translations en.json (German)

[ci skip]

* New translations en.json (Greek)

[ci skip]

* New translations en.json (Basque)

[ci skip]

* New translations en.json (Finnish)

[ci skip]

* New translations en.json (Hebrew)

[ci skip]

* New translations en.json (Hungarian)

[ci skip]

* New translations en.json (Italian)

[ci skip]

* New translations en.json (Japanese)

[ci skip]

* New translations en.json (Korean)

[ci skip]

* New translations en.json (Kurdish)

[ci skip]

* New translations en.json (Lithuanian)

[ci skip]

* New translations en.json (Dutch)

[ci skip]

* New translations en.json (Punjabi)

[ci skip]

* New translations en.json (Polish)

[ci skip]

* New translations en.json (Portuguese)

[ci skip]

* New translations en.json (Russian)

[ci skip]

* New translations en.json (Slovak)

[ci skip]

* New translations en.json (Slovenian)

[ci skip]

* New translations en.json (Swedish)

[ci skip]

* New translations en.json (Turkish)

[ci skip]

* New translations en.json (Ukrainian)

[ci skip]

* New translations en.json (Chinese Simplified)

[ci skip]

* New translations en.json (Chinese Traditional)

[ci skip]

* New translations en.json (Vietnamese)

[ci skip]

* New translations en.json (Galician)

[ci skip]

* New translations en.json (Portuguese, Brazilian)

[ci skip]

* New translations en.json (Persian)

[ci skip]

* New translations en.json (Khmer)

[ci skip]

* New translations en.json (Tamil)

[ci skip]

* New translations en.json (Bengali)

[ci skip]

* New translations en.json (Marathi)

[ci skip]

* New translations en.json (Norwegian Nynorsk)

[ci skip]

* New translations en.json (Kazakh)

[ci skip]

* New translations en.json (Latvian)

[ci skip]

* New translations en.json (Azerbaijani)

[ci skip]

* New translations en.json (Hindi)

[ci skip]

* New translations en.json (Burmese)

[ci skip]

* New translations en.json (Chinese Traditional, Hong Kong)

[ci skip]

* New translations en.json (Sinhala)

[ci skip]

* New translations en.json (Uzbek)

[ci skip]

* New translations en.json (Norwegian Bokmal)

[ci skip]

* New translations en.json (Occitan)

[ci skip]

* New translations en.json (German, Switzerland)

[ci skip]

* New translations en.json (Bengali, India)

[ci skip]

* New translations en.json (Kabyle)

[ci skip]

* New translations en.json (Karakalpak)

[ci skip]

* New translations en.json (Romanian)

[ci skip]

* New translations en.json (Dutch)

[ci skip]

* Auto commit: Calculate translation coverage

* chore: list languages crossing the coverage threshold vs production in the l10n PR description

* docs: Crowdin upload notes in AGENTS.md

* docs: Crowdin translation workflow in AGENTS.md

* New translations from Crowdin: fill ar/fa/ko gaps, fix Excalidraw+ in RTL (ar/fa/he), ar diamond term

* Auto commit: Calculate translation coverage

* New translations from Crowdin: fill the editor gaps for the E+ languages (cs, de, es, fr, hi, hu, it, ja, pl, pt-BR, ru, uk, zh-CN)

* Auto commit: Calculate translation coverage

* New translations from Crowdin (Czech): objekt for elements, Poznámka, Mód pro čtení, Zobrazit mřížku, Zamknout nástroj

* New translations en.json (Indonesian)

[ci skip]

* New translations en.json (Thai)

[ci skip]

* New translations en.json (Romanian)

[ci skip]

* New translations en.json (French)

[ci skip]

* New translations en.json (Spanish)

[ci skip]

* New translations en.json (Arabic)

[ci skip]

* New translations en.json (Bulgarian)

[ci skip]

* New translations en.json (Catalan)

[ci skip]

* New translations en.json (Czech)

[ci skip]

* New translations en.json (Danish)

[ci skip]

* New translations en.json (German)

[ci skip]

* New translations en.json (Greek)

[ci skip]

* New translations en.json (Basque)

[ci skip]

* New translations en.json (Finnish)

[ci skip]

* New translations en.json (Hebrew)

[ci skip]

* New translations en.json (Hungarian)

[ci skip]

* New translations en.json (Italian)

[ci skip]

* New translations en.json (Japanese)

[ci skip]

* New translations en.json (Korean)

[ci skip]

* New translations en.json (Kurdish)

[ci skip]

* New translations en.json (Lithuanian)

[ci skip]

* New translations en.json (Dutch)

[ci skip]

* New translations en.json (Punjabi)

[ci skip]

* New translations en.json (Polish)

[ci skip]

* New translations en.json (Portuguese)

[ci skip]

* New translations en.json (Russian)

[ci skip]

* New translations en.json (Slovak)

[ci skip]

* New translations en.json (Slovenian)

[ci skip]

* New translations en.json (Swedish)

[ci skip]

* New translations en.json (Turkish)

[ci skip]

* New translations en.json (Ukrainian)

[ci skip]

* New translations en.json (Chinese Simplified)

[ci skip]

* New translations en.json (Chinese Traditional)

[ci skip]

* New translations en.json (Vietnamese)

[ci skip]

* New translations en.json (Galician)

[ci skip]

* New translations en.json (Portuguese, Brazilian)

[ci skip]

* New translations en.json (Persian)

[ci skip]

* New translations en.json (Khmer)

[ci skip]

* New translations en.json (Tamil)

[ci skip]

* New translations en.json (Bengali)

[ci skip]

* New translations en.json (Marathi)

[ci skip]

* New translations en.json (Norwegian Nynorsk)

[ci skip]

* New translations en.json (Kazakh)

[ci skip]

* New translations en.json (Latvian)

[ci skip]

* New translations en.json (Azerbaijani)

[ci skip]

* New translations en.json (Hindi)

[ci skip]

* New translations en.json (Burmese)

[ci skip]

* New translations en.json (Chinese Traditional, Hong Kong)

[ci skip]

* New translations en.json (Sinhala)

[ci skip]

* New translations en.json (Uzbek)

[ci skip]

* New translations en.json (Norwegian Bokmal)

[ci skip]

* New translations en.json (Occitan)

[ci skip]

* New translations en.json (German, Switzerland)

[ci skip]

* New translations en.json (Bengali, India)

[ci skip]

* New translations en.json (Kabyle)

[ci skip]

* New translations en.json (Karakalpak)

[ci skip]

* New translations en.json (Romanian)

[ci skip]

* New translations en.json (Uzbek)

[ci skip]

* New translations en.json (Danish)

[ci skip]

* New translations from Crowdin: fit the promo banner variants to the EN width in all languages; shorter Share for mr/ku, add kk/my

* Auto commit: Calculate translation coverage

---------

Co-authored-by: dwelle <5153846+dwelle@users.noreply.github.com>
2026-11-19 14:25:26 +00:00
9fbd8468f2 fix(editor): tear down an open text editor when the app unmounts (#12688)
Unmounting with a text editor open left its listeners on the window,
holding on to the app and its scene until one of them next fired.

The editor is now torn down with the app. Nothing is written: what was
typed is in the last change the app reported.

Co-authored-by: Márk Tolmács <14922478+mtolmacs@users.noreply.github.com>
Co-authored-by: sahargavriely <63425950+sahargavriely@users.noreply.github.com>
2026-11-19 14:10:19 +01:00
David Luzar 894589f399 feat(editor): keep editing text when the window loses focus (#12675)
Co-authored-by: Márk Tolmács <14922478+mtolmacs@users.noreply.github.com>
Co-authored-by: sahargavriely <63425950+sahargavriely@users.noreply.github.com>

* feat(editor): keep editing text when the window loses focus

The text editor submitted on any blur, the window's included: switching
to another tab or app and back ended the edit.

- submit only when the focus moves elsewhere in the document
- until the user types, and while the window is away, the editor shows
  the scene's text, so a change made in another tab or by a collaborator
  is there to go on from
- the editor closes when its element is deleted or removed from outside
- collab: a text being edited takes newer remote copies. Its editor holds
  the draft and writes it on top, so the clients end up on the same text
- excalidraw-app: the tab sync no longer ends a text edit

* fix(editor): keep the text editor open when the update that removed its element brings it back

The editor closes when its element is gone from the scene, deferred to
after the update. A reset followed by a load of the same scene removes
and restores the element in one go, and the deferred close then wrote the
draft over the restored text.
2026-11-19 13:08:26 +01:00
David Luzar d732d4f3d5 fix(editor): text auto-resize follow-ups (#12672)
* Revert "feat(editor): show the side of an edited text that can be dragged to wrap it"

This reverts commit baf95e5ce (part of #12634): drawing the hovered
side of an auto-resizing text while it's edited adds too much visual
noise. The resize cursor on the side handle stays.

* fix(editor): keep editing a text unwrapped from its auto-resize toggle

Clicking the auto-resize toggle on the box of the text being edited
landed on the canvas, which the editor took for a press outside it and
submitted. The editor now handles the press, keeping the text edited.

* fix(editor): keep a rotated text's anchor in place when toggling auto-resize

The point a text's alignment pins was kept in the text's unrotated frame,
but a rotated text turns about the center of its box, which (un)wrapping
moves: on the canvas, the text shifted. Keep the anchor where it's drawn.
2026-11-18 15:04:16 +01:00
David Luzar 9fbeaed54a feat(app): rotate promo banner messages per editor load (#12664)
Pick one of several promos (presentations, MCP, comments, teams, voice chat, CLI) at random on load, each with its own icon and utm_content. The CLI promo links to its GitHub repo in a blue variant.
2026-11-17 22:59:00 +01:00
David Luzar 680f58ccfd feat(app): return 404 for unknown paths (#12654)
* feat(app): return 404 for unknown paths

- vercel: drop the framework preset's catch-all to index.html, keep a rewrite for /excalidraw-plus-export
- add a static 404 page (excluded from the SW precache and the sitemap)
- service worker: serve the cached app shell only for / and APP_ROUTES
- APP_ROUTES list + test that it matches the vercel.json rewrites
- remove the dead web share target (nothing handled POST /web-share-target)
- robots.txt: simplify to what it already meant (allow all)

* fix(app): let the 404 page scroll and shrink on short screens

* feat(app): add Excalidraw+, docs and CLI links to the 404 page

* feat(app): add MCP link to the 404 page

* feat(app): track 404 page views on excalidraw.com
2026-11-17 18:08:12 +01:00
David Luzar c0a0ca348f feat(editor): pick the flowchart Alt+arrow target by a single distance score (#12646)
* fix(editor): Enter/Esc only close the shape switch popup

Esc no longer also deselects, and Enter no longer enters text/line editing.

* feat(editor): pick the flowchart Alt+arrow target by a single distance score

Replace the in-line/linked/cone/past-edge tiers with one score per node
(forward + (k * sideways)² / forward), so the nearest node that looks next in
the pressed direction wins; links only break near-ties.
2026-11-16 16:23:22 +01:00
David Luzar 82190fb28f feat(editor): w wrap tweaks: frame what's inside the selection, keep unbound containers (#12638)
* fix(editor): keep restored z-indices on undo/redo unless taken

Undo/redo generated a new fractional index for every element it moved in
the z-order, even when the restored index was still valid. Later history
entries refer to the original indices, so undoing several z-order changes
in a row could restore a different stacking order.

* fix(editor): frame deselected elements within the selection on `w`

Wrapping the selection in a frame now also takes in deselected elements
that are inside the selection's bounds, or overlap them while reaching out
by no more than the frame's padding (the frame grows to fit them; a frame
around an image keeps the image's size). Groups go in whole.

The frame takes the place of its lowest child in the z-order instead of
going on top, so that it stays below the elements overlapping it.

* feat(editor): `w` keeps the containers it unbinds texts from

Unwrapping a labeled container with `w` now unbinds its text and keeps
both selected, as the "unbind text" action does. Only a container that
`w` itself wrapped a text in is removed, while the selection stands.

The next `w` puts the unbound texts back into their containers as they
sat in them.
2026-11-15 17:23:19 +01:00
David Luzar 9e9621b873 feat(editor): text auto-resize: resize from the editor, Alt+W toggle, wider wrap when zoomed out (#12634)
* fix(editor): keep the text auto-resize toggle on the box while typing

The toggle was positioned from `appState.editingTextElement`, the element
as it was when editing started, so it stayed put as lines were added or
removed. Resolve the current element instead, for the hit test too.

* feat(editor): resize a text from its sides while editing it

Dragging the left or right side of the free text being edited sets the
width it wraps at, without leaving the editor (a mere click there still
submits). The edited text isn't reliably the selection, so the drag is
handled by the editor rather than the selection's transform handles —
with grid and object snapping, as when resizing on the canvas.

* feat(editor): let a typed or pasted text grow wider when zoomed out

Below 100% zoom, the width a text wraps at is TEXT_MAX_WRAP_WIDTH on
screen rather than in scene units, up to TEXT_MAX_WRAP_WIDTH_ZOOMED_OUT.

* feat(editor): toggle text auto-resizing with Alt+W

On the selected free texts (on if any of them wraps, else off) and on the
text being edited. Turning it off keeps the text's width, wrapping at it —
at the width a typed text stops growing at, if wider.

Zen mode (Alt+Z) now goes by the key's letter too where the layout gives
one, as on AZERTY both would otherwise claim the key labelled W.

* feat(editor): hint at Alt+W for a wrapped text and while editing a text

The hint for editing now also takes precedence over the one for a selected
text: a text just created is selected while it's edited.

* feat(editor): show the side of an edited text that can be dragged to wrap it

A text that doesn't wrap yet has no box showing its sides while it's
edited: the side under the pointer is now drawn (dashed, as the box of a
wrapped text), along with the resize cursor.

* fix(editor): no stale cursor or hidden transform handles around a text being edited

- the canvas kept the cursor of what was hovered before editing (the
  selected text's move cursor, a resize handle's), which flashed once the
  pointer left the editor: it's reset as editing starts
- a text just created is selected while it's edited, so its transform
  handles, which aren't drawn then, still resized it (ending the edit)

* fix(editor): no gap or cursor flash between a text's editor and its side handles

- the side handles of the text being edited get a hit test of their own:
  the selection's left the pixel at the text's right edge to neither the
  editor nor the handle
- the canvas is given, from over the editor, the cursor of what the pointer
  would leave the editor onto: the browser shows the canvas' cursor as it is
  when the pointer gets there, and what the canvas then sets a frame later

* fix(editor): give a text made to keep its width a pixel to spare

A text exactly as wide as its longest line is on the verge of wrapping:
Chrome lays the editor's text out in 1/64px steps, rounding each run of it
up (a line being split into more runs as it's edited), so the line could
wrap in the editor alone.
2026-11-15 13:10:59 +01:00
David Luzar 3a317b55f5 fix(editor): stop centered text lines jittering while typing (#12623)
* fix(editor): stop centered text lines jittering while typing

The text editor was placed by `left`/`top` and zoomed by a scale
transform. Browsers round a scaled element's layout offset to whole
pixels, so as a center- or right-aligned text grows (moving the editor
by fractions of a pixel) its other lines shifted by up to 1px per
keystroke at any zoom other than 100%. Place the editor by the
transform's translate instead, which is kept exact.

* fix(editor): stop the other lines' glyphs shimmering while typing

- Anchor the editor's transform at the text's alignment point (origin
  0 0), so it doesn't move while typing; only the box's own anchor
  (a whole or half px) changes.
- Give non-wrapping editors a whole-px width, so the browser's rounding
  of each line's centering offset stays constant. Wrapping editors keep
  their exact width, where the canvas wraps the text too.
- Grow the editor's box to its text when a font's glyphs overflow it,
  so the browser doesn't scroll the text to reveal the caret on each
  keystroke (which shifted the other lines).

* test(editor): update the text editor style snapshot for its new placement
2026-11-14 13:47:03 +01:00
David Luzar 01dc5ec62e feat(editor): anchor keyboard zoom on the caret while editing text (#12622) 2026-11-14 11:07:30 +01:00
David Luzar 82d5847e57 feat(editor): ui.disabled.minimap; zoom buttons without the minimap toggle (#12606)
* feat(editor): ui.disabled.minimap; zoom buttons without the minimap toggle

- `ui={{ disabled: { minimap: true } }}`: a new opt-out form of the `ui`
  prop, the full default UI minus the controls listed. Removes the minimap
  and every way to toggle it (footer button, Preferences item, command
  palette and context menu entries), through the minimap action's predicate
- without the minimap toggle (removed by `ui.disabled.minimap`, or the
  reduced UI of `ui.enabled`), the zoom controls are the zoom out / zoom
  level / zoom in buttons again instead of the zoom menu: their
  PanelComponents, styles and zen-mode rules are restored from before #12605
- `isUIControlEnabled` handles both forms and is on AppClassProperties; the
  props comparator compares either form generically

Claude Opus 5.5 (xhigh)

* docs(editor): changelog for the minimap, zoom menu and ui.disabled

Claude Opus 5.5 (xhigh)

* fix(editor): hide the zen-mode zoom buttons from keyboard focus

The −/+ buttons' own `visibility: visible` (.ToolIcon_type_button--show)
overrode their wrappers' `visibility: hidden` in zen mode, so Tab still
focused the invisible buttons. Hide the buttons too, at the end of the
wrappers' fade.

Claude Opus 5.5 (xhigh)
2026-11-12 18:58:27 +01:00
Dan DekkerandMark Tolmacs 609f0f2fff perf(editor): avoid redundant canvas transforms for cached elements (#12489)
Signed-off-by: Mark Tolmacs <mark@lazycat.hu>
Co-authored-by: Mark Tolmacs <mark@lazycat.hu>
2026-11-12 17:46:09 +01:00
David Luzar 1440f2d2f8 feat(editor): minimap + zoom menu (#12605)
* feat(editor): add a toggleable minimap

- bottom-left above the canvas actions; toggled via the footer button,
  Alt+M, the context menu, command palette and Preferences
  (`appState.minimapEnabled`, browser-persisted)
- elements drawn as single-color blocks (polylines for lines/arrows/
  freedraw, outlines for frames), rendered in a web worker on an
  OffscreenCanvas with a main-thread fallback; the controller, renderer and
  worker are lazy-loaded chunks
- drag the viewport (or press outside of it to center it), limited to one
  viewport size past the content, with edge auto-pan; wheel zooms around
  the viewport center
- locked viewports keep the minimap scale frozen while rubberbanding and
  snapping back; `viewport.beginGesture()` holds the overscroll during the
  drag
- the viewport rect turns opaque when small; the styles panel stays clear
  of the minimap (and the tablet pen-mode button); unavailable in editors
  shorter than 500px
- theme class is now applied before state-change listeners run
- `Scene.onUpdate` unsubscribe no longer throws after the scene is destroyed

Claude Fable 5.2 + Claude Opus 5.5 (xhigh)

* feat(editor): zoom menu in place of the zoom buttons

- the zoom island holds the zoom level and the minimap toggle (sharp where
  they meet); the -/+ buttons are gone
- clicking the zoom level opens a menu: zoom in/out, reset zoom, and the
  three zoom-to-fit actions, each with its shortcut
- zoom level's pressed/focus rings are inset, so the toggle can't cover them
- smaller gap between the styles panel and the minimap
- zoom in/out/reset actions no longer render their own buttons

Claude Fable 5.2 + Claude Opus 5.5 (xhigh)

* feat(editor): zoom menu fit items, no minimap shortcut, announcement dot

- zoom menu: zoom in/out, then "Zoom to fit" (Shift+1), "Zoom to
  selection" (Shift+2) and "Reset zoom" (Shift+0, which it already
  accepted); "Zoom to fit selection" (Shift+3) is no longer listed
- minimap: drop the Alt+M shortcut (action, help dialog, tooltip, menus)
- TEMPORARY pulsing dot on the minimap toggle announcing the minimap,
  until 2026-11-19, for editors that loaded with content; dismissed for
  good once the minimap is opened
- "Show hints" preference renamed "Toolbar hints"

Claude Opus 5.5 (xhigh)

* chore(repo): remove the minimap scroll-lock demo button

The dev-only "Scroll lock demo" button and the commented-out initialState
in excalidraw-app were for testing the minimap against a locked viewport
and aren't meant to ship.

Claude Opus 5.5 (xhigh)
2026-11-12 17:01:41 +01:00
David Luzar 701b901a0f docs(repo): redirect the bare docs.excalidraw.com root too (#12559)
Vercel compiles redirect sources with strict path-to-regexp, so "/:path*"
matches "/foo" but not "/". The root kept serving the old Docusaurus page.
"/(.*)" matches the root as well.

Opus 5.5 (xhigh)
2026-11-05 18:10:20 +01:00
Milos Vetesnik 0c9b449be6 docs(repo): redirect docs.excalidraw.com to plus.excalidraw.com/docs/sdk (#12537)
* docs(repo): redirect docs.excalidraw.com to plus.excalidraw.com/docs/sdk

The developer docs moved to the Excalidraw+ docs. Every old page redirects to its new location, and anything else redirects to the docs home.

* docs(repo): redirect the mermaid-to-excalidraw docs to their own section

The package's docs moved to plus.excalidraw.com/docs/mermaid-to-excalidraw, rewritten for v3.
2026-11-05 17:22:51 +01:00
David Luzar 7ded689cad feat(editor): bump mermaid-to-excalidraw to 3.6.0 (elbow flowcharts, Gantt, quadrant charts, timelines) (#12535)
* feat(editor): bump mermaid-to-excalidraw to 3.3.0 (Pele 1.13, stepped edges)

- mermaid-to-excalidraw 3.1.0 -> 3.3.0 (Pele 1.8.0 -> 1.13.0): flowchart
  edges and state transitions are elbow arrows when the definition asks for
  a stepped curve (`curve: "step"`, `linkStyle … interpolate step`); class
  namespaces are drawn as boxes like subgraphs (3.2.0)
- Pele 1.13 reports syntax errors on the source line (counting front matter,
  directives, comments and blank lines) and errors past the end on the last
  line, so the TTD dialog no longer converts them: the conversion would shift
  them twice

Claude Opus 5.5 (low)

* docs: link #12535 in the changelog

Claude Opus 5.5 (low)

* feat(editor): draw Mermaid flowchart and state edges as elbow arrows

Convert Mermaid diagrams (TTD dialog and paste) with `flowchart.curve:
"step"` (`MERMAID_TO_EXCALIDRAW_CONFIG`), which m2e 3.3 turns into elbow
arrows for flowchart edges and state transitions. A curve the definition
sets itself (front matter, `%%{init}%%`, `linkStyle … interpolate`) still
wins; class and ER diagrams are unaffected.

Claude Opus 5.5 (low)

* feat(editor): elbow arrows for Mermaid flowcharts only (mermaid-to-excalidraw 3.4.0)

mermaid-to-excalidraw 3.4.0 replaces `flowchart.curve` with `elbow`, per
diagram type. Use `elbow: { flowchart: true }`: state diagrams' elbow
transitions need more work in m2e, so they stay as before.

Claude Opus 5.5 (low)

* feat(editor): bump mermaid-to-excalidraw to 3.5.0 (Gantt, quadrant charts, timelines)

mermaid-to-excalidraw 3.5.0 converts Gantt charts, quadrant charts and
timelines to Excalidraw elements instead of an image. The Mermaid dialog's
description lists them (and State diagrams, missing before), its syntax
links built by one helper.

Claude Opus 5.5 (low)

* fix(editor): detect pasted Mermaid after comments and front matter

Pasted text was only taken for Mermaid when its diagram type came first,
or after a single one-line `%%{...}%%` directive. Skip everything Mermaid
allows before it: blank lines, `%%` comments, directives (also over
several lines) and front matter.

A directive doesn't run past the next `%%{`, so text with many unclosed
directives is checked in linear time (searching each to the end of the text
would be quadratic: ReDoS).

Claude Opus 5.5 (low)

* feat(editor): bump mermaid-to-excalidraw to 3.6.0 (diagram types loaded on first use)

mermaid-to-excalidraw 3.6.0 loads each diagram type's parser and converter
on first use: its main chunk is 20.3 KiB (brotli) instead of 35.8, plus
1.5–5.1 KiB for the type converted (a first flowchart: 28.5 KiB).

Claude Opus 5.5 (low)
2026-11-04 20:53:43 +01:00
David Luzar dd2f8fc32b fix(editor): don't clip arrows to their frames (#12516)
* fix(editor): don't clip arrows to their frames

Arrows (and their labels) are no longer clipped to the frame they belong
to, so they can connect elements across and out of frames. They stay
members of their frame, so they're still moved, copied, deleted and
exported with it.

- Not clipped on the canvas or in SVG, and hit (click, hover, box and
  lasso selection) outside their frame too.
- Exporting a frame includes other frames' arrows reaching into it, as it
  does other non-children overlapping it.
- Moving a frame (dragging it, with the arrow keys or from the stats
  panel) keeps its arrows bound to the elements that don't move with it,
  instead of unbinding them. Their free points move with the frame, elbow
  arrows are routed once per move and keep their fixed segments.
- mutateElement no longer ignores an elbow arrow's x/y update to 0.

Fixes #6749
Fixes #7827

Claude Opus 5.5 (xhigh reasoning)

* docs(changelog): arrows aren't clipped to frames

Claude Opus 5.5 (xhigh reasoning)

* fix(editor): take arrows out of frames once neither of their ends is in them

An arrow belongs to its frame only while one of its ends is in it: bound to
an element in the frame, or, unbound, inside it. Checked when an arrow is
finished (drawn, or an end dragged), when a drag ends (the dragged arrows and
those bound to the dragged elements), and when a frame's children are
recomputed (resize, grouping). An arrow bound only to elements outside its
frame thus no longer gets cut, duplicated or exported with it.

Claude Opus 5.5 (xhigh reasoning)

* fix(editor): take arrows out of frames when nudged or moved from the stats panel

The arrow keys and the stats panel move arrows too, so check there as well
whether a moved arrow still has an end in its frame.

Claude Opus 5.5 (xhigh reasoning)
2026-11-03 09:20:50 +01:00
David Luzar 8bcdca4526 fix(editor): ignore deleted elements when inserting frame children (#12510)
fix(editor): place new frame children below the frame despite deleted children

Deleted frame children keep their frameId and index, so one left above the
frame made new children of that frame (created or dragged in) go above it,
up to the top of the canvas, until a reload dropped the deleted elements.
Only live children count now.

Claude Opus 5.5 (xhigh)
2026-10-31 17:48:47 +01:00
David Luzar 2610ebae0c feat(editor): Alt+arrows move to the flowchart node that's visually next (#12502)
* feat(editor): Alt+arrows move to the flowchart node that's visually next

Alt+arrow navigation used to follow only the arrows bound to the pressed
side of the selected node, cycled through siblings on repeated presses,
and fell back to any linked node when nothing was that way.

It now picks, among the nodes of the selected node's flowchart, the
nearest node of the first non-empty tier:
1. nodes in line (sharing the row for left/right, the column for up/down)
2. linked nodes whose center lies past the selected node's edge
3. nodes whose center lies in the 45° cone of the pressed direction
4. any other node whose center lies past that edge

Near-ties (within 10%) go to linked nodes, successors first, then
reading order. Pressing the opposite of the last move goes back where it
came from, also after releasing Alt.

Claude Opus 5.5 (xhigh)

* docs(packages/excalidraw): changelog for visual flowchart navigation

Claude Opus 5.5 (xhigh)

* feat(editor): forget the way back when Alt is released

Going back where the last Alt+arrow move came from only applies while Alt
is still held; a new Alt session navigates from scratch.

Claude Opus 5.5 (xhigh)

* feat(editor): drop the Alt+arrow way back

Pressing the opposite of the last move no longer returns to the node it
came from. As an override it beat even nodes in line (B ← went back down
to A instead of to C in B's row); navigation is now stateless, so a key
from a given node always goes to the same place.

Claude Opus 5.5 (xhigh)

* feat(editor): link flowchart nodes through non-elbow arrows too

Any arrow bound at both ends now links its nodes, for Alt+arrow
navigation and for the nodes Ctrl+arrows keeps new nodes clear of.

Claude Opus 5.5 (xhigh)

* fix(editor): break flowchart navigation ties by alignment before reading order

Of two equally near in-line nodes, both linked, Alt+arrow went to the
upper one even when the other was level with the selected node's center.
Offsets within a pixel still tie, so float noise in fanned-out siblings
doesn't decide between them.

Claude Opus 5.5 (xhigh)

* perf(editor): walk flowchart links in one pass over the scene

Collecting a node's flowchart rescanned every arrow in the scene for each
node visited, so Alt+arrow and Ctrl+arrow in a large chart paid chart
nodes × all arrows (~10 ms per press at 1,000 nodes). A neighbour map
built in one pass makes it linear.

Claude Opus 5.5 (xhigh)
2026-10-31 11:51:48 +00:00
David Luzar a758e93d6a fix(editor): restore centered flowchart node creation (#12500) 2026-10-30 20:19:53 +01:00
David Luzar b99a49dbeb perf(editor): load Mermaid diagram code per diagram type (mermaid-to-excalidraw 3.1) (#12481)
* perf(editor): bump @excalidraw/mermaid-to-excalidraw to 3.1.0

3.1.0 loads Pele's code per diagram type, on first use (`pele/lazy`),
instead of all 33 diagram types at once: a first flowchart downloads
~66 KiB (brotli) instead of ~217 KiB. The per-diagram chunks are only
reachable through the lib's dynamic import, so `lazyChunksPlugin` keeps
them out of the PWA precache.

Claude Opus 5.5 (xhigh)

* chore(editor): name Pele's diagram chunks in TTD chunk-load comments

Since mermaid-to-excalidraw v3, it's Pele (not Mermaid) that lazy-loads
a chunk per diagram type, as of 3.1.0.

Claude Opus 5.5 (xhigh)

* feat(app): cache all Mermaid chunks for offline use once the TTD dialog opens

mermaid-to-excalidraw 3.1 splits Pele into a chunk per diagram type,
which aren't precached. With 3.0, the single Pele chunk cached on first
use covered every diagram type offline; now only the types converted
while online would.

`lazyChunksPlugin` emits the list of mermaid chunks as a hashed JSON
asset, which index.html points to with a `<meta>` (+33 B br). Once the
TTD dialog is opened, the app fetches the list and the chunks (after 5 s,
so the dialog's own chunks aren't fetched twice, at low priority) for the
service worker to cache in `lazy-chunks` (~200 kB br on top of what the
dialog loads). App only: package hosts (e.g. E+) are unaffected.

Claude Opus 5.5 (xhigh)
2026-10-30 12:10:15 +01:00
David Luzar e7b534668a ci(repo): measure each master commit against the one before it (#12484)
GitHub's hosted runners differ from run to run (region, CPU), so a commit's
timings only compare with timings from the same runner.

- The perf job builds the commit and master before the push and loads both
  alternately (`yarn stats:compare --base <commit> --iterations 6`), instead of
  waiting for staging; without staging there's nothing to cancel, so every merge
  gets its run.
- `perf.mjs --base` takes a commit: checked out into a temporary worktree with its
  own dependencies, built and served like this checkout. `--out *.json` writes both
  builds' loads; `--wait-for` is gone. One unrecorded warm-up load per build, and
  the runner's CPU in the environment.
- `post.mjs` sends the commit time (the admin orders runs by it) and the base
  build; perf runs need one.

Claude Opus 5.5 (xhigh)
2026-10-28 16:29:35 +01:00
David Luzar 14bb42edee feat(editor): lay Mermaid diagrams out with Pele (mermaid-to-excalidraw v3) (#12480)
* chore: type-check linked packages' `@excalidraw/excalidraw/{element,common}/*` imports against the sources

Packages linked into the monorepo (e.g. a local `@excalidraw/mermaid-to-excalidraw`)
import types from `@excalidraw/excalidraw/element/*` and `.../common/*`, which
didn't map to the sources and fell back to the linked package's own (published)
copy of `@excalidraw/excalidraw`, failing the type check. The mocked arrows in
the Mermaid tests now use the `LocalPoint` their points are typed as.

Claude Opus 5.5 (xhigh)

* feat(editor): TTD Mermaid errors on their source line, with guidance by diagram type

- Mermaid (and Pele) number lines as they parse the definition: without its
  front matter, directives, comment lines and leading blank lines (and in
  flowcharts and ER diagrams, a line ending with a comment runs on into the
  next one). Errors are now mapped back to the line of the source they're on
  for the highlighted line, the summary, the shown message, the auto-fixer and
  the AI repair prompt. Errors past the end (e.g. a missing `end`) are on its
  last non-empty line.
- The likely causes depend on the diagram type: an unclosed class body,
  composite state or entity (not "a decision node"), sequence blocks missing
  their `end`, labels with brackets or parentheses that need quoting, `end`
  used as a node.
- Definitions without a (known) diagram type get a summary and hint, and their
  first line is highlighted. Mermaid and Pele word that error differently.

Claude Opus 5.5 (xhigh)

* feat(editor): auto-fix more common Mermaid mistakes in TTD

New auto-fix candidates (each still only offered if it parses):

- quote labels with brackets or parentheses in them:
  `A[Process (main)]` -> `A["Process (main)"]`
- close unclosed blocks (`subgraph`/`loop`/... `end`s, class/state/entity
  `}`s) where their indentation ends, not only at the end of the definition
- close a node label left open before its edge (`A[Start --> B` ->
  `A[Start] --> B`), and drop closing brackets that close nothing
- `->` -> `-->` in flowcharts and state diagrams (labels left alone)
- `end` used as a flowchart node -> `End`
- the `:` missing before a sequence message's or ER relationship's label
- an invalid flowchart direction -> `TD`
- a misspelled diagram type (`flowchar TD`, `sequencediagram`), or a missing
  one

Claude Opus 5.5 (xhigh)

* feat(editor): fix and explain invalid or misplaced directions in TTD Mermaid

- A flowchart subgraph's `direction` is uppercased (`lr` -> `LR`), `TD` is
  `TB` there (unlike in the flowchart's header), and one that isn't any
  direction is dropped, for the subgraph to keep the flowchart's.
- A direction on the first line of a class, state or ER diagram
  (`classDiagram LR`, `erDiagram direction LR`) is moved to a `direction`
  statement on the next line, unless the diagram has one already.
- Sequence diagrams have no direction: it's dropped from their first line and
  their `direction` statements.
- The likely causes explain all of these.

Claude Opus 5.5 (xhigh)

* feat(editor): mark TTD assistant messages rendered with Pele

Assistant messages are saved with the chat with `renderer: "pele"`, to tell
their diagrams from those of chats saved before mermaid-to-excalidraw v3,
which Mermaid rendered (and which can't be told apart later).

Claude Opus 5.5 (xhigh)

* feat(editor): paste `swimlane-beta` diagrams as Mermaid

mermaid-to-excalidraw v3 converts them (Pele renders them, Mermaid doesn't),
but pasting one inserted it as text, as `swimlane` wasn't a diagram type
that marks pasted text as Mermaid.

Claude Opus 5.5 (xhigh)

* feat(editor): lay Mermaid diagrams out with Pele (mermaid-to-excalidraw 3.0.0)

mermaid-to-excalidraw 3.0.0 parses and lays out diagrams with Pele instead
of Mermaid, which is no longer bundled. It keeps labels where Pele placed
them along their arrows with `label.labelPosition`, which skeleton arrows
support since #12425.

Claude Opus 5.5 (xhigh)

* docs: changelog for mermaid-to-excalidraw v3 and skeleton bound arrows

Claude Opus 5.5 (xhigh)
2026-10-27 17:35:28 +01:00
David LuzarandMark Tolmacs c711e80ec5 fix(editor): route elbow arrows with a single corner where one fits (#12458)
* fix(editor): route elbow arrows with a single corner where one fits

Elbow arrows keep a padding around the elements they connect, and enter
the end element from the edge of it. When the end element is closer to the
start's side than that (e.g. just below it), the route stepped aside to that
edge first, with a few pixels' jog.

When the elements can be connected with a single corner instead (leaving the
start and entering the end the way they head, both legs clear of both
elements, the legs with arrowheads long enough to fit them), that route is
used, before (and instead of) routing on the grid.

As a leg without an arrowhead can be short now, changing the arrowheads of
an elbow arrow (from the picker, by flipping it, or by pasting styles)
routes it again, to make room for them.

Claude Opus 5.5 (xhigh)

* fix(editor): route elbow arrows with two corners where they fit

When the arrow leaves the start element and enters the end one heading the
same way (e.g. from the bottom of one to the top of another below and to the
side of it), and they're closer than the padding the arrow keeps around
them, the route had a few pixels' jog between the two paddings.

Such arrows are now routed with two corners, the same way as with a single
one: turning halfway, as on the grid when there's room. When only one end
has an arrowhead, and halfway would leave it a shorter leg than the
padding, the turn moves toward the other end (keeping enough of that leg to
round its corner).

Claude Opus 5.5 (xhigh)

* fix(editor): keep elbow arrows' simple routes when their fixed segments go

When an element moves so that an elbow arrow's segment lines up with its
fixed one (e.g. moving the start element a grid step, onto the fixed
segment's level), they're merged and the fixed segment dropped, and the
arrow re-routed, as when a fixed segment is released. That re-route went
straight to the grid, without trying the one or two corner route first,
which left the jog that route avoids until the arrow was routed again.

Any route on the grid now tries the simple route first.

Claude Opus 5.5 (xhigh)

* refactor(editor): route and clean elbow arrows in one place

routeElbowArrow() now tries the one or two corner route, falls back to the
grid, and removes short segments and points between collinear ones, so its
three callers don't repeat that. They also pass getElbowArrowData()'s result
through, rather than destructuring and rebuilding it.

Claude Opus 5.5 (xhigh)

* refactor(editor): name elbow arrow route getters and updates apart

routeElbowArrow() returns a route's points, and rerouteElbowArrow() an
element update routing the arrow again, so they're getElbowArrowRoute() and
updateElbowArrowRoute() now (and the grid routing getElbowArrowGridRoute()).

Claude Opus 5.5 (xhigh)

* fix(editor): draw elbow arrows' jogs too short to see straight

While an element bound to an elbow arrow is moved so that a fixed segment
lines up with the ones around it, the arrow keeps a zero-length jog between
them until it's released, and rough.js drew the jog's two corners as a knot.

A segment shorter than 1px between two longer ones heading the same way is
now drawn straight. Corners of short segments in a row, and short U-turns,
keep their corners.

Claude Opus 5.5 (xhigh)

* fix(editor): keep elbow arrows' simple route legs long enough to round

A leg of the one or two corner route without an arrowhead only had to
outlast the cleanup of short segments (1px), so the route could leave stubs
a few pixels long (e.g. from the side of one element to the facing side of
another just below and beside it, with no arrowheads). Their corners lost
their rounding, and the arrow looked like a line hugging the element,
coming from the wrong side.

Every leg is now longer than half the corner radius, keeping at least a
quarter of the rounding, and one with an arrowhead also fits it. Shorter
legs go to the grid routing instead.

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>

* fix(editor): keep elbow arrows' simple routes clear by the binding gap

The one or two corner route kept a fixed 5px from the elements it connects,
rather than the binding gap the arrow keeps at its ends (which grows with
the element's stroke). Where an element's bounds reach past the point the
arrow binds to (e.g. an ellipse or a diamond entered below its top), a leg
could pass closer to it than that, and over a thick stroke.

The route now keeps clear of each element by its binding gap.

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>

* refactor(editor): check elbow arrow route legs with doBoundsIntersect()

segmentCrossesBounds() repeated doBoundsIntersect()'s overlap check, so it
now passes it the segment's bounds instead.

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>

* refactor(editor): tidy up the elbow arrow route getters

getSimpleRoute() worked out the last leg of a one corner route also for two
corner ones, which then replaced it, and took a Pick<> of the data its only
caller passes whole. getElbowArrowGridRoute()'s doc listed parameters it
doesn't take.

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>

---------

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>
Co-authored-by: Mark Tolmacs <mark@lazycat.hu>
2026-10-27 16:49:38 +01:00
David LuzarandMark Tolmacs 808d068e18 fix(packages/excalidraw): update arrow binding on skeleton transform (#12425)
* fix(element): don't store movePoints() options on linear elements

`LinearElementEditor.movePoints()` passed its `otherUpdates` straight into
`mutateElement()`, so the `moveMidPointsWithElement` option ended up as a
property on every arrow updated through its bindings. Only the bindings are
element properties now.

Claude Opus 5.5 (xhigh)

* feat(element): position skeleton arrow labels with `label.labelPosition`

`convertToExcalidrawElements()` always centered an arrow's label halfway
along it. A skeleton arrow's `label` can now set `labelPosition` (0-1 along
the arrow's path, as bound arrow labels store it), e.g. to keep a label
where a layout engine placed it.

Claude Opus 5.5 (xhigh)

* fix(element): place skeleton bound arrows where binding puts them

`convertToExcalidrawElements()` bound arrows to elements but kept the
endpoints the skeleton gave, which aren't where Excalidraw puts the ends of
bound arrows. The first time their bindings were updated (e.g. on undo/redo,
or moving an element they're bound to) the arrows jumped there, e.g. by up to
~50px for arrows converted from Mermaid diagrams. Bound arrows are now placed
where their bindings put them once all elements are converted.

Claude Opus 5.5 (xhigh)

* fix(element): measure and frame skeleton bound arrows as placed

Placing bound arrows in `convertToExcalidrawElements()` re-measured their
labels without the given render environment (`updateBoundElements()` now
forwards one to `handleBindTextResize()`), and ran after frames were sized
around them, so a label rewrapped by its shortened arrow could stick out of
its frame. Arrows are now placed before frames are sized.

Claude Opus 5.5 (xhigh)

* fix(element): don't skip placing arrows listed by elements they aren't bound to

Placing skeleton bound arrows skips arrows already updated through another
element, but marked every arrow an element's `boundElements` listed as
updated, though `updateBoundElements()` only updates those bound to it. A
stale entry on an element placed earlier kept the arrow from being placed.

Claude Opus 5.5 (xhigh)

* fix(element): don't grow arrow height to fit rewrapped labels

Review finding 1.

The skeleton placement pass in convertToExcalidrawElements() calls
updateBoundElements(), which calls handleBindTextResize() for arrows with
labels. When the label rewraps taller than getBoundTextMaxHeight() allows
(for arrows under 80px tall, that is the label's old height), it set the
arrow's `height` from the text, leaving it inconsistent with its points.

Reproduction steps:
convertToExcalidrawElements() with rectangles A (0,0,100x20) and
B (500,0,100x20), an arrow at (100,10) with points [[0,0],[400,0]] bound
from A to B with label "aaaa bbbb cccc dddd eeee fff", and a frame
containing all three. Placement shortens the arrow, so the label wraps to
2 lines (height 25 -> 50).

Failure case:
observed arrow height 130 (50 + 80 padding) with points [[0,0],[388,0]];
expected 0, as the points are horizontal. The stale height persists
through updateScene() and inflates later getBoundTextMaxHeight() results.
The same happens in the editor: dragging the end point of a horizontal
labelled arrow (linearElementEditor.test.tsx) left it at height 130.

Fix:
handleBindTextResize() no longer grows arrow containers to fit their
label, matching redrawTextBoundingBox(), which already exempts arrows:
an arrow's size derives from its points, and its label is positioned
along them rather than within its height. The label itself still
rewraps. The linearElementEditor inline snapshot that recorded the
bogus height of 130 for a horizontal arrow is updated to 0.

* fix(element): keep skeleton arrow labels where labelPosition put them

Review finding 2.

A skeleton arrow's `label.labelPosition` is a fraction of the arrow's path
as given (the only path a caller such as a layout engine knows), but the
placement pass (updateBoundElements() on bound arrows) then shortens both
ends by their binding gaps, and the stored fraction was resolved against
the shortened path. Unless both ends were trimmed equally, the label no
longer sat where the caller put it.

Reproduction steps:
convertToExcalidrawElements() with rectangles A (0,0,100x100) and
B (400,0,100x100), and an arrow at (80,50) with points [[0,0],[250,0]]
bound from A to B, label { text: "LABEL", labelPosition: 0.25 }. The
fraction denotes x = 80 + 0.25 * 250 = 142.5 on the arrow as given.
Placement moves the start to x = 106 (off A by the gap) and keeps the end
at 330. Label center measured with
LinearElementEditor.getBoundTextElementPosition().

Failure case:
observed label center x = 162 (0.25 of the placed 106..330 path), expected
142.5: 19.5px off. Other inputs: arrow 60..440, labelPosition 0.8 rendered
at 336.4 instead of 364 (-27.6px); arrow 100..400, labelPosition 0.25 at
178 instead of 175 (+3px).

Fix:
convertToExcalidrawElements() records the point a given labelPosition
denotes on the arrow as given, and after placing bound arrows re-derives
labelPosition as the parameter of the closest point on the placed path,
so the label stays at that point. Default labels (no labelPosition given)
are re-projected as an explicit 0.5 is: a layout engine that omits it
(mermaid-to-excalidraw does, for every edge label) puts its labels at the
midpoints of its routes as given. A point on a stretch placing trimmed
off projects onto the arrow's end, so the label is kept as close to it as
it can be while clear of the arrow's ends and arrowheads
(clampLabelPositionOffEnds()). The closest-point
projection is extracted from handleBoundTextDragging() into
LinearElementEditor.getPathParameterAtPoint() and reused, unchanged.

* fix(element): clamp skeleton arrow label positions as restore does

Review finding 3.

Reproduction steps:
- Call `convertToExcalidrawElements` with arrows whose
  `label.labelPosition` is 5, -1, NaN, Infinity or -Infinity, both
  unbound and bound to two rectangles via `start`/`end`.
- Read `labelPosition` off the resulting text elements.

Failure case:
- Unbound arrows: 5 -> stored 5, -1 -> stored -1 (expected 1 and 0,
  what `restore` would produce via `clamp(v, 0, 1)`).
- Bound arrows: already 1 and 0, only because the placement pass
  re-derives `labelPosition` from the placed path.
- NaN/Infinity/-Infinity: 0.5 on both, since `cloneJSON` of the skeleton
  turns them into `null`, which falls back to the default.

Fix: `bindTextToContainer` now normalizes an arrow label's
`labelPosition` the way `restore` does: finite values are clamped to
[0,1], anything else falls back to DEFAULT_BOUND_TEXT_LABEL_POSITION.
This covers every arrow label at creation, independent of the cloneJSON
side effect and of whether the placement pass touches the arrow. The
`labelPoints` lookup is unaffected, as `getPointAtPathParameter` already
clamps and rejects non-finite values.

* fix(element): store skeleton arrow label x/y where placed arrows put them

Review finding 4.

Placing bound arrows (updateBoundElements) moves and shortens them and
rewraps their labels via handleBindTextResize, which sets the label's
new width/height but, for arrow containers, never its x/y. The labels
convertToExcalidrawElements returned kept the x/y computed for the
arrow as given and the label as first wrapped.

Reproduction: convertToExcalidrawElements with rectangles A(0,0,100x20)
and B(500,0,100x20), and an arrow at (100,10) with points (0,0)-(400,0)
bound A->B, labelled "aaaa bbbb cccc dddd eeee fff". Compare the
label's stored x/y with LinearElementEditor.getBoundTextElementPosition
on the returned elements.

Failure case (observed vs expected, i.e. derived from the placed arrow):
- in a frame, or not: x=160, y=-2.5 (240x50) vs x=180, y=-14.998
- with labelPosition 0.25: x=60, y=-2.5 vs x=80, y=-14.998
- short label "hi" (no rewrap): y=-2.5 vs y=-2.498 (the old 0.5px drift)
Consumers reading label.x/y directly, rather than through
getTextElementWithAccuratePosition, saw the box ~20px off.

Fix: in transform.ts, in the loop after placement that re-derives
labelPosition, also set every placed arrow's label x/y to
LinearElementEditor.getBoundTextElementPosition, after labelPosition is
final. All labels of placed arrows get it, given labelPosition or not.

Not fixed in handleBindTextResize: the editor deliberately treats arrow
label x/y as a cache. The renderer, bounds, hit testing and the WYSIWYG
editor derive them from the arrow every time (see the doc comment on
getTextElementWithAccuratePosition). Writing them there would change
editor history/snapshots for no visible effect. convertToExcalidrawElements
returns the elements as data, so its stored x/y should be right. Before
this branch they were, up to 0.5px.

Tests: a regression test checks that stored label x/y match the placed
arrow, with and without labelPosition. It fails before the fix (160 vs
180). Two exact x/y assertions on "HELLO WORLD!!" labels became
toBeCloseTo. Four snapshots change: label x/y now follow the placed
arrows (sub-pixel in y, up to ~3px in x where placement is asymmetric),
and version goes 3 -> 4 from the extra mutation.

* fix(excalidraw): strip leaked moveMidPointsWithElement on restore

`LinearElementEditor.movePoints()` used to spread its `otherUpdates`
straight into `mutateElement()`, so the `moveMidPointsWithElement` option
was persisted as a property on every arrow/line updated through its
bindings. 25902dc3b stopped writing it, but scenes saved before that
still carry it, and `restoreElementWithProperties()` keeps unknown keys
(it spreads `...element` and only deletes `strokeSharpness` and
`boundElementIds`), so the junk prop survived every load and kept
travelling through saved files, collab payloads and history deltas.

Reproduction steps:
- Call `restoreElements()` on an arrow carrying
  `moveMidPointsWithElement: false` and a line carrying
  `moveMidPointsWithElement: true` (new test in restore.test.ts).

Failure case:
- Observed: the restored arrow still has
  `moveMidPointsWithElement: false` ("expected { id: 'id1', type:
  'arrow', ... } to not have property "moveMidPointsWithElement"",
  received `false`).
- Expected: the prop is not an element property and is dropped.

Fix:
- Delete `moveMidPointsWithElement` alongside the other stripped legacy
  props in `restoreElementWithProperties()`, and type it as a deprecated
  input prop there.

History: the leak was introduced by c141960ad ("feat: Non-elbow arrow
snapping and behavior changes (#9670)"), merged to master on
2025-11-25, and it is still present on master. It is not in any npm
release tag (v0.18.0, v0.18.1), but it shipped via master builds
(excalidraw.com and `@next` prereleases) for ~11 months, so real
scenes carry the prop.

Review finding 5.

* refactor(element): pass moveMidPointsWithElement as a movePoints option

Review finding 6.

Reproduction / evidence: `LinearElementEditor.movePoints()` took
`moveMidPointsWithElement` in its `otherUpdates` argument (typed next to
`startBinding`/`endBinding`), which is the bag of element updates forwarded
to `_updatePoints()` and from there into `scene.mutateElement()`. Callers:

- `updateBoundElements()` (binding.ts) passed
  `{ moveMidPointsWithElement: <same element at both ends> }` as
  `otherUpdates` - the only caller setting a real value.
- `LinearElementEditor` point dragging (two call sites) forwarded
  `updates?.moveMidPointsWithElement` from `PointMoveOtherUpdates`, but
  `pointDraggingUpdates()` never sets that field, so it was always
  undefined there.

Before 25902dc3b this put `moveMidPointsWithElement: false/true` on every
arrow updated through its bindings (and bumped its version). 25902dc3b
fixed it by copying only `startBinding`/`endBinding` out of `otherUpdates`
in the non-elbow branch of `_updatePoints()`.

Failure case: `otherUpdates` still mixed a behaviour flag with element
properties, so the filter in `_updatePoints()` had to know about every
non-property key. Any new option added to `otherUpdates` the same way
would be silently persisted on linear elements (and saved to scenes)
unless the filter was updated too.

Fix: move `moveMidPointsWithElement` into `movePoints()`'s existing
`options` parameter, next to `isBindingEnabled` /
`isMidpointSnappingEnabled`, and drop it from `otherUpdates` and from
`PointMoveOtherUpdates` (along with the dead forwarding at the two drag
call sites). `otherUpdates` now only holds element properties, so the
non-elbow branch of `_updatePoints()` spreads it directly again, as on
master; `mutateElement()` skips undefined values, so explicitly undefined
bindings remain no-ops. The elbow branch's binding filtering is untouched.
Behaviour is unchanged (no snapshot changes). Added a test that the option
still keeps midpoints moving with the element and isn't stored on it.

* refactor(element): place skeleton bound arrows once each, per arrow

Review finding 8.

The placement pass in `convertToExcalidrawElements` simulated moving every
bindable element (`updateBoundElements` per bindable) and repurposed
`simultaneouslyUpdated` as an "already placed" ledger (a fresh copy per
call to dodge the id-set cache), then re-collected the arrows each call
touched for the label loop. Its correctness hinged on `updateBoundElements`
internals: updating both ends from either one, the `doesNeedUpdate` stale
`boundElements` filter, and the array-identity id cache. It already broke
once (fdc8262d5).

Reproduction / evidence: a scratch vitest dumped the output (minus seeds,
nonces and timestamps, versions kept) of `convertToExcalidrawElements` for
arrows bound across two shapes, to the same shape at both ends (2- and
4-point), elbow arrows (one and two ends bound), arrows in frames, six
arrows on one labelled hub, text ends with ids referenced before the
elements, and multi-point arrows, and spied on `movePoints`. Every bound
arrow was placed exactly once.

Failure case: none found. Skeleton bindings all go through `applyBinding`,
which always lists the arrow on the bindable, so the ledger never skipped
or double-placed an arrow. This is a maintainability fix.

Fix: extract the per-arrow body of `updateBoundElements`' visitor into an
exported `updateBoundArrow` (`updateBoundPoint` for each binding, then
`movePoints` with `moveMidPointsWithElement` for arrows bound to one
element at both ends, then `handleBindTextResize`), and call it from
`updateBoundElements`. Dropped the visitor's per-binding `changedElement`
check: after `doesNeedUpdate`, one end is always bound to `changedElement`,
so it always held. The transform pass now iterates the arrows bound to
elements present and places each once, re-deriving its label's
`labelPosition` and x/y in the same loop. No ledger, no copies of it, no
per-bindable calls. Outputs of the scratch dump, versions included, are
byte-identical before and after; all existing tests and snapshots pass
unchanged.

* fix(element): don't nudge skeleton arrow ends by 0.5px

bindLinearElementToElement() moved every skeleton arrow's start 0.5px
towards its end and its end 0.5px towards its start, "so bindings don't
overlap with start/end bound element coordinates" (#7195). The placement
pass now re-places every bound end with updateBoundArrow(), which puts
it off the bound element by the binding gap, so for bound ends the
nudge was dead work (a clone, nudge and normalize that's overwritten).
It only still had an effect on ends nothing re-places: the unbound end
of half-bound arrows, and both ends of unbound arrows (including those
whose start/end reference missing ids, which bind nothing).

Reproduction (convertToExcalidrawElements, regenerateIds: false):
- fully bound: rect A (0,0,100x100), rect B (400,0,100x100), arrow at
  (100,50) points [0,0]->[300,0], start A, end B
- half bound: rect A, arrow at (100,50) points [0,0]->[300,100], start A
- half bound: rect B, arrow at (100,50) points [0,0]->[300,0], end B
- start: { id: "nope" } (missing), and an arrow with no start/end, both
  at (100,50) points [0,0]->[300,0]

Failure case (observed -> expected):
- fully bound: x 106, points [0,0]->[288,0], version 5 both with and
  without the nudge (it's fully overwritten)
- half bound (start): unbound end at (399.5, 149.5) -> (400, 150)
- half bound (end): unbound start at x 100.5 -> 100
- missing ref / unbound: x 100.5, points [0,0]->[299,0] while width
  stays 300 (stale, getNormalizeElementPointsAndCoords() doesn't update
  it) -> x 100, points [0,0]->[300,0], width 300

Fix: remove the nudge (and the single point early return that only
guarded it), so ends are either placed by their bindings or kept where
the skeleton puts them. Bound ends can't be left unplaced: the bound
elements are always added to the element store, and updateBoundPoint()
only skips degenerate arrows the nudge didn't change either.

Snapshot changes: the unbound arrows in "should transform linear
elements" and "should transform to labelled arrows when label provided
for arrows" now keep x as given (100/450 instead of 100.5/450.5) and
points spanning their width ([0,0]->[100,0] instead of [99,0]). Their
labels don't move (the arrow midpoints are unchanged). The "should bind
arrows to existing elements if ids are correct" assertion, whose ids
are missing and so bind nothing, now expects x 255 as given (was 255.5).

Adds a regression test that a half-bound arrow's unbound end and an
unbound arrow stay where the skeleton puts them.

Review finding 9.

* perf(element): measure skeleton arrow labels once, as placed

Review finding 11.

`bindTextToContainer` ran `redrawTextBoundingBox` on every label, so an
arrow's label was wrapped and measured against the arrow as given, then the
placement pass (`updateBoundArrow` -> `handleBindTextResize`) wrapped and
measured it again against the arrow shortened by its binding gaps, always
throwing the first result away.

Reproduction: a scratch vitest mocked `wrapText` / `measureText` with
counters and converted two shapes and a 400px arrow bound to both with the
label "aaaa bbbb cccc dddd eeee fff".

Failure case: observed wrapText x2 (maxWidth 280, then 271.6) and
measureText x3 (newTextElement's unwrapped measurement, the discarded
redraw, the placed rewrap); expected wrapText x1, measureText x2. Six
labelled arrows on one shape: wrapText 13, measureText 20 (now 7 / 14).
Unbound labelled arrows were already measured once (wrap 1 / measure 2).

Fix: `bindTextToContainer` no longer measures arrow labels; the transform
records them, the placement pass drops each label `updateBoundArrow` just
measured, and the labels left (of arrows not placed) are measured after it
with `redrawTextBoundingBox`, as before. Nothing between creating a label
and the pass reads its size: binding only sets `startBinding` /
`endBinding` (no points), `labelPoints` is still taken on the input arrow,
and for arrow containers `handleBindTextResize` ignores the old label
height. Measuring the leftovers after the pass, rather than predicting at
creation which arrows get placed, means no label can go unmeasured.

A scratch dump of 18 scenarios (bound / one end / same shape both ends /
elbow / created and text ends / missing end id / ids before data / frame /
single point / autoResize: false / labelPosition in and out of range /
unbound / hub of six / shape labels) is identical before and after (seeds,
nonces and timestamps stripped, versions kept), except the label `version`
of placed arrows, one lower for the dropped mutation; the 4 snapshot
changes are exactly that. Added a test asserting the wrap / measure counts
for a bound and an unbound labelled arrow (fails before: 3 wraps vs 2).

* fix(editor): re-measure bound labels with the host's render environment

Review finding 12.

The finding: the `renderEnvironment` option this branch added to
`updateBoundElements` (a9b2d2878) was passed only by the transform, and
since e0f198c15 not even by that (it calls `updateBoundArrow` directly),
so the option was dead while documenting that it "measures the labels of
the updated arrows". Meanwhile every editor path re-measured bound labels
with the default environment, ignoring the host's
`<Excalidraw renderEnvironment>` (its custom `textMetrics`), so a label
laid out with the host's metrics re-wrapped the first time its arrow was
touched.

The re-wrap itself predates this branch: master's `updateBoundElements`
never took an environment and called `handleBindTextResize(element,
scene, false)`, as `LinearElementEditor`'s point drag still did. Rather
than drop the dead option, this wires it (and the other label-measuring
editor paths) to the host's environment.

Reproduction: convert two rectangles A, B and an arrow bound to both,
labelled "aaaa bbbb cccc dddd eeee ffff", with
`convertToExcalidrawElements(..., { renderEnvironment })`, whose
`textMetrics.getLineWidth` is `text.length * 5`. Move B by 1px and call
`updateBoundElements(B, scene)` as the drag path does. In the editor:
render `<Excalidraw renderEnvironment={env}>` with the same scene and drag
or arrow-key nudge B, align A and B, undo/redo the drag, or drag the
arrow's point.

Failure case (this branch and master alike):
  observed: "aaaa bbbb cccc dddd eeee ffff", width 145, becomes
            "aaaa bbbb cccc dddd\neeee ffff", width 190
  expected: unchanged, "aaaa bbbb cccc dddd eeee ffff", width 145

Cause: no editor caller passed `updateBoundElements` an environment, so
it called `updateBoundArrow` without one; `ElementsDelta`'s redraw,
`LinearElementEditor`'s point drag and `listMarker`'s re-numbering
likewise measured without one.

Fix: optional `renderEnvironment` threaded the way resize already does it
(a trailing param, or an option where the function takes an options bag):
- `updateBoundElements`: its existing option is now passed by the editor
  (doc comment updated); `updateBindings` gains the same option and
  forwards it. Both pass it to `updateBoundArrow`.
- drag: `dragSelectedElements` (new trailing param), from the selection tool.
- arrow-key nudge (App.tsx).
- align / distribute: `alignElements` / `distributeElements` (new trailing
  param), from their actions.
- rotate/resize: the `updateBoundElements` calls in `transformElements`,
  `rotateMultipleElements`, `resizeSingleElement`, `resizeMultipleElements`
  now pass the environment they already had.
- sticky notes: `updateStickyNoteLayout` passes its `renderEnvironment` on
  to its bound-arrow pass.
- undo/redo: `ApplyToOptions.renderEnvironment` reaches
  `ElementsDelta.redrawElements` (both the bound-text redraw and the
  bound-arrow pass); `History.undo/redo` and `HistoryDelta.applyTo` take
  it, the history actions pass `app.renderEnvironment`, and
  `App.applyDeltas` defaults to it.
- `LinearElementEditor` point drag: `handleBindTextResize` gets
  `app.renderEnvironment`.
- list-marker re-numbering on duplicate (`advanceDuplicatedListMarkers`,
  `applyListMarkerAdvances`, new trailing param): both its label redraw and
  its free-text refresh.
- the remaining editor callers of `updateBoundElements` / `updateBindings`,
  each of which can move a labelled arrow bound to the element: text
  editing (App.text, textWysiwyg), duplicate, crop/uncrop, wrap/unwrap
  (also its `redrawTextBoundingBox`), font/style/auto-resize actions,
  element type conversion, and the Stats position/angle/dimension inputs
  (`moveElement` gets a trailing param).

Left alone:
- `updateBindings`' arrow branch (`updateArrowBindings`): it only rebinds
  the arrow's ends and measures no label.
- `transform.ts`: already measured with its environment (via
  `updateBoundArrow`).
- callers that already passed `app.renderEnvironment` to
  `redrawTextBoundingBox` / `handleBindTextResize` (resize, Stats font
  size, font/bound-text actions, textWysiwyg submit, type conversion).
- `updateBoundElements` re-measures only arrow labels (its visitor skips
  non-arrows), so no non-arrow container label path needed changing there.
- free-text measurement helpers called directly (`measureText`, `wrapText`,
  `refreshTextDimensions`, ...) outside these bound-label paths: not part
  of this finding.

Without the prop, `app.renderEnvironment` is the owner-window environment
with no `textMetrics`, so measurement still falls back to the global
provider or a canvas; single-window behaviour is unchanged (no snapshot
changes). All new params are optional, so external callers are unaffected.

Tests: a direct `updateBoundElements` test (packages/element) and editor
tests rendering `<Excalidraw renderEnvironment>` for drag, nudge, align,
undo/redo and arrow point drag; each fails without its path's change.

* refactor(element): build one scene in skeleton conversion, resync it

convertToExcalidrawElements built a temp `scene` from the element store
before labels and the elements skeleton arrows bind to were created, and
then a second `boundScene` from the completed store for the bound-arrow
placement pass, so the function held two scenes over overlapping element
objects (Review finding 13).

Evidence that the divergence produces no wrong output: the early scene
is only used to measure non-arrow container labels (the container and
label are passed directly; the sticky fit gets its label explicitly) and
by bindBindingElement (geometry from the arrow and the element passed
in; the map is only consulted for a text's container, and containers are
always in the snapshot). This was already so on master, where the same
snapshot scene was used the same way. To check, the scene was
temporarily resynced (replaceAllElements) after every store addition,
including before each bindBindingElement, and outputs were diffed
against the current code (reseeded, ids canonicalized) for created
rectangle/ellipse/diamond/text ends, elbow arrows, existing ids bound by
two arrows (copied twice), text ends, a labelled sticky note, a frame
around them, and an arrow label (given its own id) used as another
arrow's start: all identical, and the full suite passed in that mode.

So this is a maintainability fix: drop `boundScene` and resync the one
scene with replaceAllElements once the store is complete, which is what
`new Scene(...)` did. Outputs, snapshots and versions are unchanged.

* fix(element): place skeleton arrows' created end shapes along the arrow

`convertToExcalidrawElements` creates a rectangle/ellipse/diamond/text for
a skeleton arrow's `start`/`end` given by `type` (no id), and placed it as
if every arrow ran left to right: the start shape left of the arrow's
`x`, the end shape right of `x + width`, both centered on the arrow's `y`.
For any other direction the shape isn't where the arrow starts or ends,
so the arrow is bound to a shape it doesn't reach, and the placement pass
(e0f198c15) then moves its ends to where those bindings put them.

Reproduction: an arrow at (0,0) with `start: { type: "rectangle" }`,
`end: { type: "ellipse" }` and
- "diagonal": points [0,0]->[100,100]
- "vertical": points [0,0]->[0,200]
- "right-to-left": points [0,0]->[-200,0]
or `end: { type: "text", text: "end" }` on the diagonal one.

Failure case (HEAD): the shapes are at (-100,-50) and (100,-50) whatever
the direction, and the ends are bound at fixedPoints the editor can't
create, outside the shapes:
- "diagonal": ellipse at (100,-50), the arrow ends at (100,100): end
  bound at fixedPoint [0,1.5].
- "vertical": end bound at [0,2.5], and the start is placed at y=56, as
  the arrow runs down the rectangle's edge.
- "right-to-left": ellipse at x=200, on the wrong side: end bound at
  [-4,0.5001], and the start is placed at x=-106, on the far side of the
  rectangle the arrow passes through.
- the text end is bound at [0,4.5] the same way.
Expected: the shapes at the arrow's start/end, the arrow pointing into
them, both ends bound on their outlines and placed off them by the
binding gap.

Fix: new `getArrowEndShapePosition` centers the shape on the arrow's
first/last segment as extended past the end, at the distance from its
center to its outline (rectangle/text box, ellipse or diamond) in that
direction, so the end lies on its outline. Explicit `x`/`y` still win,
and an existing end text still keeps its x. Left-to-right arrows are
placed as before. Other directions change, e.g. the 300x300 start
rectangle of the 395x35 arrow in "should bind arrows to existing shapes
when start / end provided with ids" moves up 13.3px, onto the arrow's
line (snapshot updated).

* fix(element): unbind unreachable skeleton arrow ends, rebind the rest

`convertToExcalidrawElements` binds skeleton arrows to their `start`/`end`
elements while it is still creating elements, and the placement pass
(e0f198c15) then places every bound end where its binding puts it. Two
kinds of bindings made at conversion time are wrong, and placing the
arrows exposes them.

1. Ends given beyond the binding area of their element

   A layout engine (e.g. mermaid's sequence diagrams, whose messages are
   bound to the participants' headers but drawn far below them) can bind an
   end the user could never bind in the editor. Its fixedPoint lies well
   outside the element, and `normalizeFixedPoint` clamps it, so the binding
   can't hold the end where it was given.

   Reproduction: rectangles A (0,0 100x20) and B (500,0 100x20).
   - "half-far": an arrow at (100,10) with points [0,0]->[450,490], start A,
     end B, so its end is given at (550,500), far below B.
   - "beyond": an arrow at (50,40) with points [0,0]->[500,0], start A, end B,
     20px below both, so beyond binding distance.

   Failure case (HEAD):
   - "half-far": end bound to B at fixedPoint [0.5001,10]. Placing moves the
     end from the given (550,500) to (550,200).
   - "beyond": both ends bound at fixedPoint [0.5001,2]. That's a binding the
     editor can't create, and it moves the arrow onto the headers the first
     time A or B is moved.
   Expected: ends beyond the binding area are left unbound where given.
   Ends within it stay bound.

   Fix: new `isPointInBindingArea` (collision.ts) checks whether a point is
   inside an element or within binding distance of its outline.
   `isEndBoundBeyondBindingArea` (binding.ts) applies it to an arrow's bound
   end. Before placing, the pass unbinds every end beyond its element's
   binding area (`unbindBindingElement`, which also drops the arrow from
   the element's `boundElements`). An arrow with no binding left isn't
   placed and keeps its geometry as given.

   The check ignores frame clipping (`getBindingCandidates` still skips
   the clipped parts of frame children): frames are sized around their
   children only at the end of the conversion, so an element given with a
   `frameId` would be checked against a 0x0 frame, and every end bound to
   it would be beyond reach. Arrows unbound from an element are still
   framed with it, as the frame pass frames what is bound to a frame's
   children (through their `boundElements`, which no longer list them).

   An end that just falls short of its element is extended onto it instead
   (`extendBoundEndOntoElement`, binding.ts): its end segment is extended
   past the end by the segment's length, at least 100px, and if that
   reaches the element, the end is moved to where it does, off the element
   by the binding gap, and stays bound. This keeps bindings a generator
   meant to make, but drew arrows slightly too short for.

   Reproduction: rectangle B (500,0 100x20), an arrow at (150,10) with
   points [0,0]->[250,0], end B, so its end is given 100px short of B.
   Expected: end bound to B, moved to (500 - binding gap, 10).

2. Ends bound before their element is sized

   A rectangle/ellipse/diamond with a label and no width/height is created
   0x0 and sized to fit its label only when its label is bound. That happens
   in the same pass that binds arrows, in skeleton order. An arrow listed
   before the element therefore binds to a 0x0 element, and
   `calculateFixedPointForNonElbowArrowBinding` binds ends on elements
   smaller than MIN_BINDABLE_SIZE to their center. Nothing recomputes the
   binding once the element is sized, so the placement pass re-aims the end
   at the center, and the result depends on element order.

   Reproduction: an arrow at (100,50) with points [0,0]->[300,0], end bound
   to B, where B is a rectangle at (400,25) with label "B" and no size
   (sized to 20x35).

   Failure case (HEAD):
     arrow listed first: endBinding.fixedPoint [0.5001,0.5001] (center),
                         points [[0,0],[294,-7.11]] (tilted)
     B listed first:     endBinding.fixedPoint [0,0.714] (left edge),
                         points [[0,0],[294,0]] (straight)
   Expected: the same in either order, the "B listed first" result.

   Fix: the pass rebinds each end that is still bound
   (`bindBindingElement`, keeping its mode) against its element as sized.
   For elements whose size didn't change after binding, this gives the
   same binding as before.

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>

* fix(editor): convert TTD dialog diagrams with the host's render environment

Review finding 7.

The text-to-diagram dialog (the Mermaid tab, and the AI chat's preview and
insert) converted mermaid's skeletons with `convertToExcalidrawElements`
without the host's `renderEnvironment`, while pasting a mermaid definition
(App.clipboard) passes `app.renderEnvironment`. So with a host's custom
`textMetrics`, every label in the dialog's conversion, container and arrow
labels alike, was measured with the default (canvas) metrics. The gap
predates this branch: d3a9c2a19 added the option and passed it from the
paste path, but not from the dialog.

Reproduction: render `<Excalidraw renderEnvironment={env}>`, whose
`textMetrics.getLineWidth` is `text.length * 5`, open the Mermaid dialog
and insert a diagram with a 100x40 rectangle labelled "aaaa bbbb cccc", and
an arrow labelled "aaaa bbbb cccc dddd eeee ffff" bound to it.

Failure case:
  preview:  both labels wrapped by the default metrics ("aaaa bbbb\ncccc",
            "aaaa bbbb cccc dddd\neeee ffff"), and the rectangle grown to
            height 60 to fit two lines
  inserted: `addElementsFromPasteOrLibrary` redraws the labels with the
            host's environment, so they end up on one line, but the
            rectangle stays 60 high, around a one-line label
Expected: as when pasting the same definition: one-line labels (70px and
  145px wide) in the preview and the scene, and the rectangle 40 high.

Fix: `convertMermaidToExcalidraw` takes an optional `renderEnvironment` and
passes it to `convertToExcalidrawElements`. Its three callers pass
`app.renderEnvironment`: the Mermaid tab's preview (whose result is what
it inserts), and the AI chat's preview (`useMermaidRenderer`, now using
`useApp`) and insert (`TextToDiagram`).

Left alone: `exportScene`, which renders the preview, takes no environment;
it draws already measured elements, so the preview's layout now matches the
inserted one.

Without the prop, `app.renderEnvironment` has no `textMetrics`, so
measurement falls back as before (no snapshot changes).

Tests: inserting from the Mermaid dialog under a host environment
(renderEnvironmentLabels.test.tsx); the rectangle's height fails without
the fix.

* fix(element): decide skeleton arrow end bindings before moving either end

When placing skeleton arrows, each end bound beyond its element's binding
area is either extended onto the element (if it just falls short) or
unbound. 61255ad73 did this one end at a time: start first, then end. For
elbow arrows, extending the start goes through `movePoints`, which reroutes
the whole arrow from both its bindings. That moved the still-bound end onto
its element before it was checked, so it was kept bound. The result
depended on which end was the start.

Reproduction: rectangles A (0,0 100x20) and B (500,0 100x20), and an elbow
arrow (`elbowed: true`) [0,0]→[400,0]→[400,490] at (150,10), bound from A
to B. Its start falls 50px short of A, and its end is at (550,500), far
below B.

Failure case:
  A→B: start extended onto A and bound, end rerouted to about (550,26)
       just under B, and left bound to B
  B→A (same arrow reversed): end extended onto A and bound, start left at
       (550,500) and unbound
Expected: both directions as B→A: the A end extended and bound, the B end
  left where given and unbound.

Fix: `extendBoundEndOntoElement` becomes `getBoundEndExtension`, which only
returns where the end would be extended to and moves nothing. The skeleton
conversion now checks both ends against the arrow as given. It unbinds the
unreachable ends first, so the reroute doesn't take them along, then
applies every extension in one `movePoints` call, then rebinds as before.

Only elbow arrows were affected: moving one end of a non-elbow arrow leaves
its other end in place. Mermaid's converter doesn't produce elbow arrows,
so this needs hand-written or LLM-generated skeletons.

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>

* fix(element): rebind elbow skeleton arrows before extending their ends

The placement pass (61255ad73, 2fe86fe7f) extends bound ends that just
fall short of their elements onto them with one `movePoints` call. Only
after that does it rebind each end against its element as sized. For
elbow arrows, `movePoints` reroutes the whole arrow from both its
bindings. A binding made before its element was sized (a labelled shape
with no width/height, listed after the arrow, is still 0x0 when the
arrow binds to it) points at the element's center. The reroute then
routes the end around the element to that center, and the rebind that
follows keeps the side the end was rerouted to. The result depended on
element order.

Reproduction: rectangle A (0,25 100x50), rectangle B at (400,25) with
label "B" and no size (sized to 20x35), and an elbow arrow
(`elbowed: true`) at (150,50) with points [0,0]->[250,0], bound from A to
B. Its start falls 50px short of A, so it gets extended.

Failure case:
  [A, B, arrow]: endBinding.fixedPoint [-0.3,0.714] (B's left side),
                 points [[0,0],[288,0]]
  [A, arrow, B]: endBinding.fixedPoint [1.3,0.5] (B's right side), six
                 points running past B to x=466 and back into its right
                 side at (426,42.5)
The same happens when the extended end is the one bound to B (the arrow
at (106,50) with points [0,0]->[224,0], ending 70px short of B), and when
both ends are extended.
Expected: the same in either order, the [A, B, arrow] result.

Fix: before extending an elbow arrow's ends, rebind both of them against
their elements as sized: an end being extended at the point it's
extended to (`calculateFixedPointForNonElbowArrowBinding` with that
point as the focus point, then `bindBindingElementToFixedPoint`), and
any other end where it is (`bindBindingElement`). Then extend, and rebind
as before.

Rebinding before the move only the ends not being extended isn't enough:
an extended end would still be rerouted to its element's center. Neither
is rebinding only after the move, because by then the reroute has
already put the end on the wrong side.

Only elbow arrows were affected: moving one end of a non-elbow arrow
doesn't reroute it, so the rebind after the move already corrects it.

Tests: "should route elbow arrows extended onto elements as to elements
sized to fit their labels after them as to those before them"
(transform.test.ts), covering the start and the end extended. It fails
without the fix (`expected 1.3 to be less than 0`).

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>

* fix(element): clamp skeleton arrow labels only off the ends they're trimmed off

ee5d10684 keeps skeleton arrow labels where `labelPosition` put them on
the arrow as given, by projecting that point onto the arrow as placed. A
point on a stretch placing trimmed off projects onto the arrow's end, so
`clampLabelPositionOffEnds` keeps the label clear of the end and its
arrowhead. But the clamp ran on the label of every bound arrow, wherever
its point projected. Labels on the arrow as placed were moved off its
ends too, which unbound (unplaced) arrows don't do.

Reproduction: rectangles A (0,0 100x100) and B (192,0 100x100), and an
arrow at (106,50) with points [0,0]->[80,0], bound from A to B. Its ends
are already off A and B by the binding gap, so placing it trims nothing.
Label widths are as measured in the tests.

Failure case:
  label "LABEL" (50px), no labelPosition:  labelPosition 0.375, center
      x=136, 10px toward the start, off the end arrowhead
  label "LABELX" (60px), no labelPosition: labelPosition 0.5, center
      x=146: too wide to clear both ends, so centered again. A 10px wider
      label jumps back 10px
  arrow [0,0]->[300,0] instead, label 220px wide at labelPosition 0.3:
      0.3667, 20px off where it was given
Expected: as on the same arrows unbound: 0.5 (center x=146) for both
  default labels, and 0.3 for the given one.

Fix: `clampLabelPositionOffEnds` returns the position unchanged unless it
is at an end of the arrow (0 or 1, within PRECISION), where points on
trimmed-off stretches project to.

Snapshot: the label in "should bind arrows to shapes when start / end
provided without ids" was too wide to clear both ends, so the clamp had
centered it at exactly 0.5. It now keeps its projected position,
0.4999999949 (and is stored at x=240 instead of 240.00000045, with its
version bumped as the position changed).

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>

* fix(element): create skeleton arrow labels unrotated

Arrow labels aren't rotated: `restore` resets their `angle` to 0, and
`redrawTextBoundingBox` asserts it outside production and resets it. A
skeleton label can still give an `angle` (its type allows the generic
element props). Until 472c87980 every skeleton label was measured with
`redrawTextBoundingBox` as soon as it was created, so an arrow label's
angle was reset there. Since then, labels of placed (bound) arrows are
measured only as placed, through `handleBindTextResize`, which leaves
`angle` as given. Labels of arrows not placed are still measured with
`redrawTextBoundingBox`, so outside production a given angle failed its
invariant.

Reproduction: rectangles A (0,0 100x100) and B (400,0 100x100), and an
arrow at (106,50) with points [0,0]->[288,0] and label
{ text: "L", angle: 1 }, once bound from A to B and once unbound.

Failure case:
  bound:   label angle 1
  unbound: "text element angle must be 0 if bound to arrow container"
           (outside production; angle 0 in production)
Expected: label angle 0 on both arrows, as after `restore`.

Fix: the label of an arrow is created with angle 0, as `restore`
normalizes it. The labels of other containers are still rotated with
them by `redrawTextBoundingBox`.

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>

* fix(element): keep skeleton loop arrows' midpoints where given

The placement pass (45276e6a9) places skeleton bound arrows with
`updateBoundArrow`, which the editor also uses as an element moves. For
an arrow bound to the same element at both ends, it passes
`moveMidPointsWithElement`, so that a loop moves with its element as a
whole: its midpoints follow its start. Placing a skeleton arrow moves
nothing it's bound to, only its ends, so a loop's midpoints followed its
start as it was placed off the element, and the loop changed shape.
Midpoints of other arrows stay where given. Only the start drags them,
so the result also depended on which end was the start.

Reproduction: rectangle A (0,0 100x100), and an arrow from A's center
around to A's right side: points (50,50) (50,-60) (160,-60) (160,50)
(106,50), bound to A at both ends.

Failure case:
  from the center: start placed off A's top edge, 56px up, at (50,-6),
      and the midpoints 56px up with it: (50,-116) (160,-116) (160,-6).
      The loop is 56px taller, and its last segment into A is diagonal
  from A's top edge (50,0): midpoints 6px up: (50,-66) (160,-66) (160,44)
  either, reversed: no change, as its start is already off A
Expected: the midpoints where given, (50,-60) (160,-60) (160,50), with
  only the ends placed.

Fix: `updateBoundArrow` takes `boundElementMoved` (default true, as the
editor calls it). The placement pass passes false, so loops are placed
like other arrows: only their ends move. Placed loops stay put under the
editor's next binding update, and still move whole with their element.

Left alone: a reversed loop given from the center still keeps its end
there. For loops, `updateBoundPoint` places the end with the arrowhead at
its fixed point and the other on the outline, and a skeleton end is bound
where given, here at the center. That's the editor's own rule from
master, applied to the binding as given.

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>

---------

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>
Co-authored-by: Mark Tolmacs <mark@lazycat.hu>
2026-10-27 16:37:03 +01:00
David Luzar 95307fa136 fix(packages/excalidraw): export PNGs from a CPU-backed canvas (#12471)
Chrome's Skia Graphite GPU canvas backend antialiases paths with 4x MSAA,
so PNG and clipboard exports came out jaggy, and large exports allocated
GPU memory many times the bitmap's size. Request a willReadFrequently
context on the export canvas before rough.canvas() creates one without
options (only the first getContext() call's options apply).

Claude Opus 5.5, xhigh
2026-10-27 16:29:21 +01:00
David Luzar cdc181c82a ci(repo): run the stats perf job on ubuntu-24.04 (#12479)
- ubuntu-latest now resolves to the 26.04 image, where Playwright 1.58 cannot install Chromium, so the first Performance run failed at Install
- a fixed image also keeps the runs comparable across runner upgrades

Claude Opus 5.5 (xhigh)
2026-10-27 15:46:41 +01:00
David Luzar 4eb1e648aa ci(repo): track bundle size and performance of master builds (#12469)
- `Stats` workflow on master: posts the production build's file sizes (raw, gzip, Brotli; initial load vs. lazy; bytes per source package) and, once staging serves the commit, its page-load and pan/zoom measurements to the Excalidraw+ backend; OSS_STATS_TOKEN lives in the master-only `stats` environment
- `scripts/stats/`: bundle-stats Vite plugin and wrapper config (`yarn stats:bundle`), the Playwright runner (`yarn stats:perf`) and the poster
- `yarn stats:compare`: builds the checkout, serves it with `vite preview` and compares it with staging (alternating loads, Mann-Whitney U test); prints a table or writes CSV with `--out`
- `excalidraw:app-start` mark in the app's entry, ending the runs' "HTML + JS" phase
- `playwright` 1.58.2 dev dependency (installs no browsers by itself)

Claude Opus 5.5 (xhigh)
2026-10-27 15:34:46 +01:00
David Luzar b7de45e881 feat(editor): fit arrowheads to short last segments & fill them along their outline (#12439)
* feat(editor): fit arrowheads to short last segments

Arrowheads used to shrink to half of the last segment, so multi-segment
arrows ending in a short segment got near-invisible heads. They now use
the whole last segment, or extend past its start where the shape allows:

- triangle: grows until its base reaches the previous segment
- arrow: widens as it shrinks (20° -> 30°), grows to half its size
  while its sides stay a stroke width off the previous segment
- circle: grows freely (no direction), also on curved arrows
- bar: ends stay closer to the tip than to the previous segment
- diamond: back vertex reaches the corner
- cardinality markers: scaled as a whole to fit the last segment
- elbow arrows: the corner rounding is taken into account

Single-segment and curved arrows keep the old sizing, except circles.

Claude Opus 5.5 (xhigh)

* fix(editor): fill arrowheads along their outline

rough.js jitters a solid fill separately from the outline (by up to 2px),
which on shapes as small as arrowheads made the fill stick out, and the
repeated closing point of triangles/diamonds drew a stray hair at the tip.

- triangle, diamond and circle arrowheads are drawn as a single rough
  stroke, and filled along that stroke
- polygon arrowheads keep their corners in place, only edges bow
- fewer ops: faster to generate and draw

Claude Opus 5.5 (xhigh)
2026-10-23 12:48:01 +02:00
Márk Tolmácsanddwelle 1d4dc2c0e6 feat(editor): Lazy load and don't precache Firebase, lazy load mermaid (#12274)
To reduce the initial bundle size and the PWA precache size, Firebase and Mermaid are now lazy loaded. Both are out of the main bundle and the PWA precache. Each is downloaded the first time it's needed and then cached by the service worker, so it also works offline after that first use.

### How it's done

Rollup splits Mermaid into many chunks with arbitrary names (one per diagram type, plus shared deps), so `globIgnores` can't match them. A small build plugin (`lazyChunksPlugin` in `excalidraw-app/vite.config.mts`) finds the chunks that are only reachable through the dynamic `import("@excalidraw/mermaid-to-excalidraw")`. It then removes them from the precache manifest. Chunks that the main bundle also uses stay precached.

A new `lazy-chunks` runtime cache (`CacheFirst`, `/assets/*.js`, max 200 entries, 90 days) stores any JS chunk that isn't precached the first time it loads.

### Offline behaviour

- **Mermaid / text-to-diagram** is no longer cached at install. It works offline once it has been opened online at least once.
- While the Mermaid library loads, the preview shows a spinner (it used to flash an error).
- If the library fails to load:
  - **Offline:** the preview shows "Couldn't load Mermaid. Check your internet connection and try again." with a Retry button. It also retries automatically when the browser comes back online.
  - **Online** (e.g. a stale app version after a deploy): the preview shows "Couldn't load Mermaid. Reload the page to try again." On `vite:preloadError` the service worker checks for an update.
  - **Chrome** keeps a failed dynamic import cached for the life of the page, so retrying can't work there. In Chrome the button reloads the page instead. The Mermaid definition being edited is saved before unload, so it isn't lost.
  - Inserting a generated diagram while the library is unavailable shows a toast with the same message. If AI generation finishes while the library can't load, the Mermaid output is validated once the library loads.
  - Pasting a Mermaid definition while the library can't load pastes it as plain text instead of failing.
- **Share / live collaboration** is hidden while offline, unless you're already in a session. This covers the top-right Share button, the main menu, the welcome screen and the command palette. An open Share dialog closes when you go offline. The online/offline state is read at startup, and changes to it are debounced by 1 s.
- **Not precached:** Mermaid and `firebaseSDK-*.js` are newly excluded. CodeMirror, font subsetting, QR code and locales were already excluded on `master`.

---------

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>
Co-authored-by: dwelle <5153846+dwelle@users.noreply.github.com>
2026-10-21 12:36:40 +02:00
Juan FernandezandMark Tolmacs 6f0a4d19b5 fix(editor): recognize Firefox/legacy WebKit quota errors in isQuotaExceededError (#11970)
- `isQuotaExceededError` in `excalidraw-app/data/LocalData.ts` only matched `error.name === "QuotaExceededError"`, the name used by Chromium and by modern Firefox (111+, since Firefox adopted the standardized DOM spec name for this error around early 2023). Older Firefox releases (pre-111) throw `NS_ERROR_DOM_QUOTA_REACHED` instead, and legacy WebKit used `QUOTA_EXCEEDED_ERR` / `code === 22`. On those engines the check silently failed, `localStorageQuotaExceededAtom` never flipped to `true`, and the quota-exceeded banner never rendered — users kept drawing with no warning that their work had stopped persisting.
- Widened the check to cover all four known spellings/codes (Chromium/modern-Firefox, legacy Firefox, legacy WebKit name, legacy WebKit code 1014/22), matching the fix suggested by @CanReader in the issue.
- Exported the function so it's unit-testable directly, and added `excalidraw-app/tests/LocalData.test.ts` covering all four cases plus a negative case (non-quota `DOMException`) and a non-`DOMException` error, to guard against over-widening the check.
- Left `excalidraw-app/sentry.ts` untouched — its quota filtering matches on error message text, not `.name`, so it's unaffected by this bug.
---------

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>
Co-authored-by: Mark Tolmacs <mark@lazycat.hu>
2026-10-20 20:25:57 +02:00
David Luzar bee01e3a12 fix(packages/excalidraw): load export fonts into a worker's font set, warn without one (#12374)
* fix: load export fonts into a worker's own font set

Since #12347 every export format loads the scene fonts before rendering,
SVG included. Without a `document.fonts` -- a DOM shim like linkedom, e.g.
Excalidraw+'s preview worker -- the loader returns early (#11997), so a
worker never loaded fonts into its own `self.fonts`, which an
OffscreenCanvas there measures and draws with.

`Fonts.loadElementsFonts` now falls back to the worker's font set, and
skips loading only where there is neither. Tested without the
`document.fonts` mock from setupTests.

Claude Opus 5.5 (xhigh)

* fix: warn once when export fonts have no font set to load into

Without a font set (Node, or a DOM shim like linkedom outside a worker)
and no `config.environment.loadFonts`, the export silently measures and
draws text with whatever fonts the environment has. Warn once per
process when the elements use fonts that would need loading (local fonts
like Helvetica never do).

Claude Opus 5.5 (xhigh)
2026-10-20 12:12:18 +02:00
David Luzar a3fdf471ee feat(editor): support Instagram embeds (#12373)
* feat(editor): support Instagram embeds

Instagram post and reel links (/p/, /reel/, /reels/, /tv/, also
username-prefixed) embed via instagram.com/<type>/<code>/embed/.
Uncaptioned so the height only depends on the media; 400x720 fits
portrait posts and reels.

Pasting Instagram's embed code works too: its loader <script> sits on a
separate line, which made the paste fall back to text.

Claude Opus 5.5 (1M context), reasoning: xhigh

* fix(editor): match loose script end tags in embed code paste

Addresses CodeQL "Bad HTML filtering regexp".

Claude Opus 5.5 (1M context), reasoning: xhigh
2026-10-20 10:06:36 +02:00
d3a9c2a195 fix(packages/excalidraw): complete cross-document runtime ownership (#11997)
* fix: complete cross-document runtime ownership

* fix: schedule cross-document animations in owner window

* fix: Prewarm the right font even if it's not Excalifont

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>

* fix: Hyperlink and tooltip host staleness issues

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>

* fix: Various hyperlink fixes

* feat: Host abstraction

* fix: exportToSvg support for document override

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>

* fix: Remove caches

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>

* fix: Refactor tests (cut non-critical)

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>

* chore: Break out host from App

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>

* fix: hold after release fixes

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>

* fix: repaint when link image decode is complete per app

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>

* chore: Font loading per-doc test

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>

* fix: Lint

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>

* fix: draw SVG frame labels without text measurement

Frame labels were baked into exports as measured, ellipsis-truncated text
elements, which made `exportToSvg` depend on a canvas (through the render
environment) for the only text it ever measures.

- add `getFrameLabel` (element package): a measurement-free label spec --
  position, font, color, arithmetic height, the frame's width as max width
- SVG: draw labels from the spec in the frame branch, full title clipped to
  the frame's width; extract `appendSvgTextLines` so text elements and
  labels produce identical markup
- canvas: unchanged output (measured, truncated text elements), now built
  from the same spec
- fit label boxes into the SVG export bounds explicitly (`extraBounds`)
- test: SVG export of a named frame succeeds with a render environment
  whose `createCanvas` throws and creates no canvas through `document`

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* fix: measurement-free embed placeholders; no render environment in SVG export

The placeholder drawn for an embed that isn't rendered live was the last
text `exportToSvg` measured, which kept a canvas (via the render
environment) in the SVG path and made headless SVG export throw on any
scene with an embed unless the process had been polyfilled.

- show the placeholder as a single line capped at 30 characters
  (`getPlaceholderLinkText`: scheme and `www.` dropped, ellipsis) instead
  of wrapping the whole link: at or below that length the existing
  `width / length` font size fits the box by construction, so nothing is
  measured, wrapped or clipped, and output is identical on every host. The
  full link stays on the element's `<a href>` in SVG
- `newTextElement` accepts pre-computed `metrics` to skip measuring
- drop `renderEnvironment` from `SVGRenderConfig`, `exportToSvg` and the
  `@excalidraw/utils` signature: SVG export's only host dependency is its
  owner document
- throw a guided error from the default canvas/image factories when there
  is no `document`/`Image`, instead of a bare ReferenceError
- tests: placeholder text capping and layout; SVG export of an iframe and
  a long-link embed with a render environment whose `createCanvas` throws

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* fix: scope top picks drag to source window

* feat: StickyNotes support

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>

* Revert "fix: measurement-free embed placeholders; no render environment in SVG export"

This reverts commit 886bea142. Rich text makes SVG export measure text
anyway (explicit x per line, run boundaries, baselines), so placeholder
labels go back to being measured and wrapped like on canvas, through the
render environment.

Kept: the guided errors thrown by the default canvas/image factories when
there is no `document`/`Image`.

Claude Opus 5.5 (xhigh)

* Revert "fix: draw SVG frame labels without text measurement"

This reverts commit 295e7d88b. SVG export measures text again (rich text
needs it regardless), so both formats go back to master's single path:
frame labels baked in as measured, truncated text elements, measured
through the export's render environment. Drops `getFrameLabel` and the
SVG label renderer.

Claude Opus 5.5 (xhigh)

* export: one `config.environment` for every format, `document` for SVG

SVG exports take the same environment as canvas ones: they measure text
(frame labels, embed placeholders) through its `createCanvas`, and are
built in its `document` (was the SVG-only `ownerDocument`).

Claude Opus 5.5 (xhigh)

* RenderEnvironment: carry the `document`

The environment is the one host parameter: its `document` is what SVG
exports are built in (the editor's owner document by default), so export
call sites pass a single environment instead of an environment plus an
`ownerDocument`. `exportCanvas` drops its `ownerDocument` option, and
`config.environment.document` defaults to the environment's.

Rich text's DOM layout will read the same member, rather than threading
`ownerDocument` through the measuring functions next to the environment.

Claude Opus 5.5 (xhigh)

* drop the process-wide `setRenderEnvironment` / `resetRenderEnvironment`

Every render and export now takes its environment explicitly: exports
through `config.environment`, the editor through its `renderEnvironment`
prop. Text measured outside both (e.g. creating elements on a server) has
`setCustomTextMetricsProvider`. A second, global way to configure the same
thing would be state shared by every job in the process, which is what
per-call export environments avoid. The default is now a constant
(the browser's).

Claude Opus 5.5 (xhigh)

* render: log per-element failures on export too, rather than throwing

As in the editor (and on master): one element that fails to render is
logged and skipped, so the rest of the exported scene survives it rather
than the whole export failing.

Claude Opus 5.5 (xhigh)

* RenderEnvironment: carry the text metrics provider

`textMetrics` replaces the per-environment registry of
`setCustomTextMetricsProvider(provider, env)`, which looked providers up
by the environment's identity, so any rebuilt environment (as exports
build one from `config.environment`) silently lost them. It now travels
with the environment, and `config.environment.textMetrics` measures an
export's text. The global `setCustomTextMetricsProvider(provider)` stays
for text measured outside both (e.g. elements created on a server).

Exports use a complete `config.environment` as-is (the editor's keeps its
caches warm), and document that it needn't be the same object across
exports. Frame label truncation measures through the environment too,
rather than on a canvas of its own.

Claude Opus 5.5 (xhigh)

* render: restore the canvas state when an element fails to draw

The scene renderer logs a failing element and carries on, but the
`save()`s it had made were never restored: its transforms and frame clip
stayed on the context for every element after it (a failing freedraw at
(80, 30) moved the next rectangle from (10, 10) to (90, 40)). Every
`save()` around drawing now restores in a `finally` (`withSavedContext`).
Pre-existing on master, in the editor and on export.

Claude Opus 5.5 (xhigh)

* export: truncate frame names down to "...", or none, to fit the frame

When not even one character plus the ellipsis fit, the frame name kept
its full title (overflowing narrow frames into their neighbors) while
reporting the frame's width. It now shrinks to just "...", and is dropped
where even that doesn't fit. Pre-existing on master.

Claude Opus 5.5 (xhigh)

---------

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>
Co-authored-by: Mark Tolmacs <mark@lazycat.hu>
Co-authored-by: dwelle <5153846+dwelle@users.noreply.github.com>
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-20 05:53:27 +02:00
David Luzar e1b7aacb35 feat(packages/excalidraw): replace the export functions with exportScene (#12347)
* [export] rewrite - init

* restore elements + filter deleted in export API (restores #11470 behavior)

* fix snaps

* port export callers added on master to the new API + snaps

- renderOverrides (#12100), sticky notes (#12064) and arrow-label hole
  (#10947) tests called the old positional exportToSvg/exportToCanvas
- embedded-scene snapshots gain master's new element fields (created,
  baseFontSize, labelPosition); decoded payloads match master's

Claude Opus 5.5 (xhigh)

* restore elements in embedded scene + json clipboard export (restores #12060 behavior)

- master's #12060 made every public export entry point restore its input
  (legacy elements reach lower-level code with `created: null`), incl. the
  PNG metadata embed and the json clipboard copy in the removed
  @excalidraw/utils wrappers
- SVG embed now serializes the restored, non-deleted elements (same as
  master's utils path), PNG embed serializes restoreElements(data.elements)
  and json clipboard copies the non-deleted restored elements
- port #12060's utils tests to the new API, observing renderers/serializer
  instead of the (now identical) scene export functions

Claude Opus 5.5 (xhigh)

* make config.canvasBackgroundColor the single export background knob

- background resolved once in configExportDimension; exportToSvg no longer
  reads appState.exportBackground (now omitted from ExportSceneData's
  appState type), and honors `canvasBackgroundColor: false`
- outline arrowheads (circle/triangle/diamond_outline, cardinality_zero_*)
  are filled with the resolved background color, also when the background
  isn't painted (as on master) — the canvas path filled them transparent,
  showing the arrow's shaft through them; SVG ignored the config color
- JPEG: `canvasBackgroundColor: false` falls back to the default background
  (+ warning) instead of rendering black; no more warning for the default
- callers (exportCanvas, ImageExportDialog, library/chart/publish previews,
  AI) pass the background via config only

Claude Opus 5.5 (xhigh)

* resolve export theme before creating frame labels

- frame labels were colored by appState.exportWithDarkMode, ignoring
  config.theme (export dialog's dark toggle), and in dark exports the
  dark-theme label color got dark-filtered again by the renderer
  (#7a7a7a -> #848484)
- theme is now resolved once in configExportDimension; dark labels are
  pre-reverted so they render with the editor's frame name color

Claude Opus 5.5 (xhigh)

* drop appState.exportWithDarkMode theme fallback in export

- `config.theme` is the only theme input (defaults to light); the type
  already omitted `exportWithDarkMode` from `data.appState`
- callers that relied on the fallback (PublishLibrary item preview, AI
  frame export) pass `theme` explicitly, keeping their behavior

Claude Opus 5.5 (xhigh)

* exportToClipboard: don't restore appState before exportToSvg (already restored there)

Claude Opus 5.5 (xhigh)

* remove unused getExportSize, type getCanvasSize's [x, y, width, height] (not Bounds)

Claude Opus 5.5 (xhigh)

* fix typos in export comments/JSDoc

Claude Opus 5.5 (xhigh)

* port with-script-in-browser example to the new export API

- exportToSvg/Blob/Canvas/Clipboard take `{ data, config }`; theme via
  `config.theme`, padding 10 kept explicit (new default is 0)
- dropped the no-op `width`/`height` appState overrides from the SVG export

Claude Opus 5.5 (xhigh)

* call getDimensions once, ignore it when widthOrHeight is set

- with an explicit `fit: "contain"`, getDimensions ran twice (the second
  time on its own output); it now supplies width/height (+ scale) once,
  and `contain` scales the content into that frame
- getDimensions + widthOrHeight both applied; widthOrHeight now wins (with
  a warning), like width/height/maxWidthOrHeight already did
- `fit: "none"` (the E+ export server path) renders identically

Claude Opus 5.5 (xhigh)

* type the export size options as mutually exclusive

- `width`/`height`, `maxWidthOrHeight`, `widthOrHeight` and `getDimensions`
  are now a union where the unused options are `?: never`, so combining
  them is a type error (runtime still ignores/warns for JS callers)
- the `never` keys are remapped over `keyof`, so every option keeps its
  JSDoc in completions & hovers (verified via the TS language service)

Claude Opus 5.5 (xhigh)

* replace getDimensions with a `scale` function, round the canvas size

- `config.scale` also accepts `(width, height) => number`, called with the
  export dimensions at scale 1 (padding included) — covers content-dependent
  scaling (e.g. E+'s pixel budgets) without the getDimensions round trip
- remove `getDimensions`: its returned `scale` replaced `config.scale` and
  multiplied the returned size, so callers thinking in output pixels had
  to divide it back out
- exportToCanvas rounds the canvas size instead of letting the canvas
  truncate it (float noise like 28.999999999999996 lost a pixel); half
  pixels now round up (frame label area 20.5px, mermaid preview 89.5px)

Claude Opus 5.5 (xhigh)

* align fit/padding/position export docs with the code

- `fit` defaults to "contain" when `width`/`height` is set, otherwise
  "none" (the doc said the opposite); dropped the unimplemented
  "x/y force none" claim
- padding is always subtracted for `maxWidthOrHeight`/`widthOrHeight`
  (they ignore `fit`), not added
- `position` values are "center" | "topLeft" (doc listed "none")

Claude Opus 5.5 (xhigh)

* derive a missing export width/height from the aspect ratio

- with `fit: "contain"` (the default when a size is given), passing only
  `width` or `height` now derives the other from the content's aspect
  ratio, as documented — it defaulted to the content's unscaled size,
  e.g. `{ height: 50 }` of 200x100 content gave a 200x50 canvas with
  60x30 content in wide empty bands (now 80x50 with padding 10)
- with `fit: "none"` the missing side stays the content extent

Claude Opus 5.5 (xhigh)

* default export `fit` to "none" when x/y is set

- `{ x, y, width, height }` was scaled to fit with `x`/`y` silently
  ignored (`fit` defaulted to "contain" whenever a size was given); an
  explicit region now crops by default, `fit: "contain"` still opts in
  (and ignores `x`/`y`, as now documented)

Claude Opus 5.5 (xhigh)

* ignore export x/y when the content is scaled to fit

- with `fit: "contain"`, `maxWidthOrHeight` or `widthOrHeight`, `x`/`y`
  shifted the fitted content by a mix of scene units and pixels; they're
  now dropped with a warning, which the previous commit already
  documented (its "ignored" claim was based on a coincidental probe)

Claude Opus 5.5 (xhigh)

* pad an export x/y region on all sides

- with `position: "center"` (the default), the centering adjustment also
  ran on axes pinned by `x`/`y`, shifting the region by the padding: the
  canvas started exactly at `x`/`y` with all padding on the right/bottom
  (`position: "topLeft"` padded all sides); `position` now only applies to
  unpinned axes, as documented

Claude Opus 5.5 (xhigh)

* consolidate exportToCanvas/Blob/Svg into exportScene({ type, data, config })

- `type: "canvas" | "png" | "jpeg" | "svg"`, return type per `type`
  (overloads, plus a union overload for dynamic callers); per-type options
  are type-checked: `quality` only for jpeg, `embedScene` for png/svg,
  `renderEmbeddables`/`skipInliningFonts`/`reuseImages` for svg
- the format replaces `mimeType` (and its "image/jpg" typo handling)
- `appState.exportEmbedScene` -> `config.embedScene` (no longer read
  from `data.appState`); `data.files` is optional
- `config.createCanvas` -> `config.environment.createCanvas` (where
  #11997's render environment and richtext's text metrics will go)
- exportToCanvas/Blob/Svg are no longer exported (no aliases);
  exportToClipboard stays, routed through exportScene
- callers, the with-script-in-browser example and tests ported

Claude Opus 5.5 (xhigh)

* export: take only scene settings from data.appState, frameRendering -> config.frames

- `data.appState` is typed as (and stripped at runtime to) the scene
  settings a .excalidraw file stores; the renderer state is built from
  those + defaults, so editor state passed in (a live AppState: open
  dialog, cropping, frame highlight…) can't affect the output. It only
  supplies the default background and what `embedScene` embeds
- `appState.frameRendering` -> `config.frames: { name, outline, clip }`
- editor callers translate their export settings via one internal
  `getExportConfigFromAppState`; `exportCanvas` drops its redundant
  exportBackground/viewBackgroundColor options
- fixes the editor's SVG export ignoring `exportScale` (the branch's
  exportCanvas SVG path had dropped it; master passed it)

Claude Opus 5.5 (xhigh)

* type export positioning options as width/height-only

- `fit`, `position`, `x`, `y`, `origin` move into the size-option union's
  `width`/`height` member, so combining them with `maxWidthOrHeight` /
  `widthOrHeight` (which ignore them) is a type error; runtime unchanged
  (still ignores/warns for JS callers)
- docs stay visible in completions (same `keyof` remap as the size options)

Claude Opus 5.5 (xhigh)

* move export `loadFonts` into `config.environment`

- font loading is a host capability, next to `createCanvas` (svg gets
  `environment: { loadFonts }` only, as it creates no canvas)

Claude Opus 5.5 (xhigh)

* changelog: export API (exportScene, config, migration table)

Claude Opus 5.5 (xhigh)

* export: default padding back to 10, canvas at least 1px

- export bounds are geometric (no stroke width), so padding 0 cut half
  of the strokes on the content's edge and made flat content (a line)
  zero-height — the library/chart/publish previews, which inherited
  master's default of 10, rendered blank thumbnails for lines
- canvas dimensions never go below 1px (a 0-sized canvas can't be
  encoded); SVG snapshot sizes are back to master's

Claude Opus 5.5 (xhigh)

* export: clamp padding against the fitted size, before deriving from it

- the padding clamp used the content's unpadded size, so flat content (a
  horizontal line) lost its padding with maxWidthOrHeight/widthOrHeight
  (`{ padding: 10, maxWidthOrHeight: 400 }` → 200x0); it now only
  considers the target being fitted into
- a missing width/height was derived before clamping
  (`{ height: 10, padding: 10 }` → 0x10, SVG viewBox NaN/Infinity)
- a zero-extent content axis no longer yields a NaN scale under contain

Claude Opus 5.5 (xhigh)

* export: clip frame exports to the frame

- frame clipping was off for exportingFrame (to avoid the rounded
  per-element clip), relying on the canvas/SVG edge — which only crops
  when the export is exactly the frame; a larger export (size options)
  painted children and overlapping elements into the margins, and SVG
  frame exports had stopped clipping (master clipped them)
- everything drawn is now clipped to the frame with square corners: a
  canvas clip after the background (`renderConfig.clipToFrame`), and an
  SVG group with the frame's clip path; the background isn't clipped

Claude Opus 5.5 (xhigh)

* changelog: fill in PR numbers for the placeholder links

Claude Opus 5.5 (xhigh)
2026-10-18 20:24:17 +02:00
Arne ReiandMahiro Hirakawa 4c37956ba5 fix(editor): detect line height from the migrated font props on restore (#12033)
* fix(editor): detect line height from the migrated font props on restore

The text branch of `restoreElement` parses the legacy `font` prop into local
`fontSize` and `fontFamily`, but line-height detection kept reading
`element.fontSize` and `element.fontFamily`. A diagram old enough to carry
`font` has neither, so `detectLineHeight` divided by `undefined` and the
element was restored with `lineHeight: NaN`. A non-numeric `height` produced
the same result.

Move the detection into `restoreLineHeight`, pass it the already-migrated
values, and fall back to the font family's fixed line height when the
detected value isn't a usable number.

---------

Signed-off-by: Mark Tolmacs <mark@lazycat.hu>
Co-authored-by: Mahiro Hirakawa <mahirohirakawa@glovrex.com>
2026-10-14 18:29:25 +02:00
David Luzar 541653c7c9 fix(editor): frame membership, clipping and cut fixes (#12270)
* fix(editor): a frame snapped to an element's edges takes it in

A new or resized frame takes the elements (and groups) within it by their
outlines (not counting the stroke), to a hair beyond its edges, which
snapping leaves them at.

Claude Opus 5.5 (1M context), effort: medium

* fix(editor): a frame always clips its children

As in SVG exports — a child inside the frame may still reach out of it with
its stroke — without checking geometry, but for children being dragged,
which are clipped only while still in it, as their drop decides. The
outline check remains for elements dragged into a frame.

Claude Opus 5.5 (1M context), effort: medium

* fix(editor): cutting a frame takes its children along

Unlike deleting it, which leaves them: they're on the clipboard with the
frame, so pasting it back would duplicate them.

Claude Opus 5.5 (1M context), effort: medium
2026-10-12 14:33:19 +02:00
Milos Vetesnik 4f310b7996 feat(app): restyle Excalidraw+ upgrade button as stacked trial CTA (#12269)
* feat: restyle Excalidraw+ upgrade button as stacked trial CTA with sparkle

* feat: use gift icon instead of sparkle on Excalidraw+ button
2026-10-12 13:28:00 +02:00
David Luzar 704db6803c feat(editor): w to wrap/unwrap selection (#12264)
* fix(editor): keep the text selected along with its container after unbinding

Claude Opus 5.5 (1M context), effort: medium

* feat(editor): `w` wraps or unwraps the selection

- a text and an empty container: binds the text
- texts (with any labeled containers): wraps each text in a container
- labeled containers: unwraps the texts and removes the containers,
  moving their arrows onto the texts; the next `w` on the untouched
  selection brings the same containers back where the texts are now
- a frame with its children, or all of a frame's children: removes the frame
- anything else without a frame: wraps it in a frame

"Wrap selection in frame" frames an image (and what lies on it) edge to
edge, and removes the frame when all of its children are selected.

Claude Opus 5.5 (1M context), effort: medium

* fix(editor): unwrapping an arrow drops its point editor

The selection unwrapping (and rewrapping, and removing a frame) leaves is
resolved with its line editor, so a deleted arrow's editor doesn't linger.

Claude Opus 5.5 (1M context), effort: medium

* fix(editor): rewrapping a note keeps the label's font size and color

A font size picked while the label was unwrapped becomes its base size, and
the note takes the label's ink (shared with binding via `getStickyNoteInk`).

Claude Opus 5.5 (1M context), effort: medium

* fix(editor): resizing an unwrapped text doesn't move its rewrapped container

A font size change keeps the text's alignment edge and middle in place, so
the move is measured there rather than at the top left.

Claude Opus 5.5 (1M context), effort: medium

* fix(editor): binding, unbinding and framing resolve the arrow point editor

Binding text to an arrow selects it with its point editor; wrapping a lone
arrow in a frame, or unbinding an arrow's label (selecting both), drops it.

Claude Opus 5.5 (1M context), effort: medium

* feat(editor): wrapping a text draws a default rectangle in the text's color

Not the current item's style — a wrapped text is a label, and the rectangle
matches it.

Claude Opus 5.5 (1M context), effort: medium

* feat(editor): unbinding keeps the text as it rendered, at a fixed width

The freed text keeps its wrapping, width and position (not auto-resizing);
rewrapping it restores auto-resize. A fixed-width text keeps its top left
through font size changes, so a rewrapped container measures the text's
move there.

Claude Opus 5.5 (1M context), effort: medium
2026-10-12 11:35:45 +02:00
David Luzar 2df993fb39 fix(editor): resizing text by a corner follows the cursor on the axis it grows most (#12262)
Text scaled by the height alone, so a corner dragged sideways didn't follow
the cursor; it now scales as resizing keeping the aspect ratio does (which
text always does), by the axis that grows most.

Claude Opus 5.5 (1M), xhigh effort
2026-10-11 16:48:34 +02:00
David Luzar ef53e5417b feat(editor): crop editor modifiers as resizing, and double-click a handle to uncrop (#12260)
* fix(editor): shift in the crop editor: shift-click keeps it open, shift-drag moves the image along one axis

- shift-clicking the image being cropped no longer toggles it out of the
  selection (which ended cropping)
- dragging the image within its crop follows the drag offset, axis-locked
  with shift as dragging elements is, applied by its change since the
  previous pointer move (pointerDownState.drag.lastOffset) so the image
  still moves back right away after being dragged past its edge
- drops App.previousPointerMoveCoords, which only the crop drag used

Claude Opus 5.5 (1M), xhigh effort

* feat(editor): alt-drag a crop handle to crop from the center

- cropElementFromCenter crops the opposite side by as much as the dragged
  one, keeping the element's center, as far as the image reaches on the
  nearer side; with shift, keeping the aspect ratio
- no alt drag threshold in the crop editor: alt-clicks don't cycle the
  selection there

Claude Opus 5.5 (1M), xhigh effort

* fix(editor): clicking a crop handle no longer leaves the crop editor

A press on a crop handle hits no element, so a click on one without a move
in between counted as a click outside the image.

Claude Opus 5.5 (1M), xhigh effort

* feat(editor): double-click a crop handle to uncrop its sides

- in the crop editor, double-clicking a side's handle uncrops that side, a
  corner's its two sides, as dragging the handle out as far as the image
  reaches does (uncropElementSides)
- with alt, the opposite side(s) too, so alt on a corner uncrops it all;
  alt double-clicks aren't ignored in the crop editor, which doesn't cycle
  the selection

Claude Opus 5.5 (1M), xhigh effort

* refactor(element): uncrop and crop from the center through one bounds helper

- cropElementToBounds crops the image to bounds relative to the element
  (rotated and flipped with it); uncropElementSides and cropElementFromCenter
  only compute those bounds
- uncropElementSides no longer drives cropElement with a pointer past the
  image's edge, copying the crop it mutates, nor recurses for the mirrored
  side
- maybeUncropSides takes the selected image, and the pointer type from
  appState.lastPointerDownWith

Claude Opus 5.5 (1M), xhigh effort

* fix(editor): arrows bound to an image follow the sides uncropped by a double-click

Claude Opus 5.5 (1M), xhigh effort

* fix(editor): crop from the drag's start, as resizing does, so alt and shift apply mid-drag

- maybeHandleCrop crops the image as it was at pointer down
  (pointerDownState.originalElements) rather than as of the previous pointer
  move, and maybeHandleResize crops in the crop editor, so pressing or
  releasing alt or shift mid-drag re-crops right away, as resizing does
- cropElement no longer mutates the crop of the element it's given (which is
  now the drag's start state)

Claude Opus 5.5 (1M), xhigh effort

* fix(editor): no invisible rotation handle in the crop editor

The crop editor draws no rotation handle, but pressing where it would be hit
it, and dragging it cropped the image ("rotation" includes "n"). A press
there is now one outside the image, which leaves the editor.

Claude Opus 5.5 (1M), xhigh effort

* refactor(element): crop an image as resizing it would resize it

- cropElement sizes the crop from the pointer as resizing does
  (getNextSingleWidthAndHeightFromPointer, from the center too), keeps it
  within the image from what stays put (the opposite side, or the center),
  and crops through cropElementToBounds; it replaces the per-handle cases,
  recomputeOrigin and cropElementFromCenter
- options as resizing's: { shouldMaintainAspectRatio, shouldResizeFromCenter }
  rather than a width aspect ratio (the element's, which is the drag's start)
- keeping the aspect ratio, a corner crops by the axis it grows most,
  relatively, as resizing does (rather than by pixels), and an axis dragged
  past what stays put has the minimal size rather than flipping
- an image already smaller than the minimal size crops no smaller, rather
  than jumping to it

Claude Opus 5.5 (1M), xhigh effort

* fix(element): the image no longer shifts by a pixel while cropping it

The crop editor drew the cropped image from its own bitmap, snapped to whole
pixels by its own corner, over the faded uncropped image's: as the corner
moved by fractions of a pixel (cropping from the center, or keeping the
aspect ratio along a side), the image within the crop shifted by a pixel
against the faded rest. Within the crop, it now draws the uncropped image's
bitmap at full opacity, clipped to the crop.

Claude Opus 5.5 (1M), xhigh effort
2026-10-11 16:37:37 +02:00
David Luzar e65eca999e refactor(editor): app.selection, and the rest of the selection tool out of App (#12258)
* refactor(editor): add AppSelection (app.selection) to select, add to, remove from and clear the selection

- select(element) for click-select, the alt-click cycle and the context menu;
  add(element) for the selection tool and the lasso's touch select (was a
  near-copy); remove(element) for shift-click; clear() replaces
  App.deselectElements and three inline copies
- isASelectedElement / isHittingCommonBoundingBoxOfSelectedElements move from
  the selection tool
- select() drops a stale line editor of a no longer selected arrow; the
  context menu no longer spreads all of this.state into its setState
- tests for the selection's frame, link selector and line editor rules

Claude Opus 5.5 (1M), xhigh effort

* refactor(editor): make the app.selection API generic over elements or ids, one or many

- select / add / remove take elements or ids, one or many (missing and
  deleted ones skipped)
- their rules become pure functions in App.selection.ts, for callers that
  need the next selection state rather than a setState (actions,
  duplication): getSelectionStateForElements (moved from @excalidraw/element,
  now keeping the current line editor), getSelectionStateAddingElements,
  getSelectionStateRemovingElements — one pass over the elements however
  many are added or removed
- remove() recomputes selectedGroupIds (it put element ids into it and lost
  the other selected groups' flags), and leaves group editing once nothing
  is selected
- the link popup on adding an element is the pointer's, not add()'s

Claude Opus 5.5 (1M), xhigh effort

* refactor(editor): move selectGroupsForSelectedElements from @excalidraw/element into App.selection.ts

- editor state (selected group ids, the edited group), used by the editor
  only; moved as is
- also ends the groups.ts <-> selection.ts import cycle in @excalidraw/element

Claude Opus 5.5 (1M), xhigh effort

* refactor(editor): move dragging the selection and box selection out of App into AppSelectionTool

- handleSelectionDragOnPointerMove: dragging the selection (or the image
  within its crop), alt-drag duplicating past the threshold
- handleBoxSelectionOnPointerMove: box selection (and of the line editor's
  points)
- handleSelectionDragOnPointerUp: frame membership of the dragged selection
- pure moves, verified mechanically
- tests for shift-dragging along one axis and moving the image within its
  crop (both untested through the pointer)

Claude Opus 5.5 (1M), xhigh effort

* refactor(editor): one check for the selection's transform handle under the pointer

- selectionTool.getTransformHandleAt() replaces the two copies in the hover
  cursor and on pointer down (line editor, elbow arrows, two-point lines,
  mobile lines, hovered line points; a lone element's or the selection's
  common bounds)
- pointer down now also ignores the handles in the element link selector,
  as the hover cursor did
- test for the resize cursor over the handles (untested)

Claude Opus 5.5 (1M), xhigh effort

* fix(editor): app.selection shows the link popup of what it selects

- select / add / remove show the link popup of a lone selected element with
  a link (or an embeddable) and hide it otherwise; clear hides it — it was
  left as is, so select() showed it only if a previous selection had
- the link editor stays open when its element is selected again
- the pointer and lasso call sites no longer set it themselves

Claude Opus 5.5 (1M), xhigh effort

* feat(editor): app.selection ends what hangs on the deselected elements and skips locked ones

- cropping ends unless the cropped image stays the selection, and an active
  embed is deactivated once deselected (the line editor already ended once
  its line is deselected)
- select / add skip locked elements, unless includeLocked — which the
  context menu passes, to offer unlocking them
- captureUpdate option, as updateScene's, to record the change for undo
- deep option on select (the elements themselves, editing their shared
  group), which Ctrl+click now goes through
- text editing isn't ended here: the editor ends itself on blur, and
  submitting it mid pointer event would commit half the event's state

Claude Opus 5.5 (1M), xhigh effort

* feat(editor): app.selection ends text editing, and add / remove / clear always end cropping

- select / add of anything but the edited text (or its container) submit
  the text editor — after the current event (it submits with a flushSync),
  and only if that editing session is still open; clear / remove leave it
  (starting text editing clears the selection)
- add / remove / clear end cropping; select keeps it only when selecting the
  cropped image again (a click inside it in the crop editor)

Claude Opus 5.5 (1M), xhigh effort

* fix(editor): app.selection derives the line editor from the final selection, and frame / deep fixes

- the line editor is set from the selection once groups are expanded: an
  arrow selected with its group (e.g. by alt-click cycling) gets none, so
  dragging from its point moves the group rather than reshaping the arrow;
  add() sets it too (adding a lone arrow left Edit / Cmd+Enter throwing)
- children of frames selected through the groups of the selected (or added)
  elements are left out, also ones selected in the same call — and adding
  within an edited group no longer deselects as if the edited group's frames
  were selected
- deep selection never expands groups (it did for elements not sharing one)
- a click-selected elbow arrow now gets its line editor on pointerdown, so
  that click's pointerup normalizes a hand-built route one gesture earlier

Claude Opus 5.5 (1M), xhigh effort

* feat(packages/excalidraw): excalidrawAPI.selection

- app.selection on the imperative API — select / add / remove / clear,
  taking elements or ids, one or many, with the deep / includeLocked /
  captureUpdate options; the type exposes only those four
- they're arrow properties, so they keep `this` when taken off the object
- changelog entry

Claude Opus 5.5 (1M), xhigh effort
2026-10-10 23:34:00 +02:00
David Luzar 4c00f31ddc feat(editor): autoplay Google Drive videos when the embed is activated (#12246)
- Drive's player has no postMessage API (unlike YouTube/Vimeo), but its
  /preview page honors `autoplay=1`, so the first activation reloads the
  embed with it: a single click plays the video in view mode
- reloaded via `contentWindow.location.replace` so it adds no history
  entry, and only once per iframe so re-activating doesn't restart it

Claude Opus 5.5 (1M), xhigh effort
2026-10-08 11:11:53 +02:00
David Luzar 2559257bb2 fix(editor): pan once and keep editing on a wheel-button drag over the text editor (#12244)
- the text editor's window pointerdown listener was added in capture mode
  but removed without it, so every past editing session kept panning too:
  the pan was multiplied by the number of texts edited since load
- the pan focuses the container, which blurred the editor while blur still
  submitted it; submit is now disabled before the pan starts, and the
  editor is refocused on release

Claude Opus 5.5 (1M), xhigh effort
2026-10-07 20:31:58 +02:00
David Luzar 53973c3a42 feat(editor): alt-click to cycle the selection through overlapping elements (#12237)
* feat(editor): alt-click to cycle selection through overlapping elements

- alt+click on the selected element (or group) selects the one below it
  under the pointer, wrapping around to the topmost
- inside an edited group, cycles through that group's elements only
- alt+drag duplicates only past a 10px threshold, so alt-clicks don't
- alt+double-click no longer creates/edits text (except with autoshape)

Claude Opus 5.5 (xhigh)

* refactor(editor): move the selection tool out of App into AppSelectionTool (app.selectionTool)

- handleSelectionOnPointerDown, clearSelection(IfNotUsingSelection),
  isASelectedElement, isHittingCommonBoundingBoxOfSelectedElements and the
  alt-click cycle target move as is
- the click selection of the pointer up handler (alt-click cycle, shift
  toggle, click select, bbox-only deselect) becomes
  handleSelectionOnPointerUp
- the selection's transform handles, maybeHandleResize / maybeHandleCrop,
  move as is
- tests for alt-click cycling, and for cropping by dragging a crop handle

Claude Opus 5.5 (1M), xhigh effort

* feat(editor): alt-click cycles the selection on its resize handles too

- alt-resizing starts only past the 10px drag threshold, as alt-drag
  duplicating does, so an alt-click on a resize handle can cycle
- an alt-click on the selected element's resize handle (over the element)
  cycles the selection, but not once a resize happened

Claude Opus 5.5 (1M), xhigh effort

* feat(editor): hint at alt-click cycling while Alt is held

- holding Alt over a single selected element (or group) with the selection
  or lasso tool shows "Alt-click to cycle selection, or drag to duplicate"
- app.modifiers tracks the held Alt, Shift and Ctrl/Cmd outside appState,
  synced from key and pointer events and reset on blur;
  app.modifiers.useHeld(modifier?) re-renders only on the given one
- the hover refresh after a pointer up replays the held modifiers, so it no
  longer releases them (the hint flickered on every alt-click)
- selectionTool.canCycleSelection() shares the cycle rules between the
  hint and the click

Claude Opus 5.5 (1M), xhigh effort
2026-10-06 17:31:23 +02:00
David Luzar ed10ac7dca feat(editor): alt-drag the text being edited to duplicate it (#12219)
* feat(editor): alt-drag the text being edited to duplicate it

- alt-pressing the text editor ends the editing and hands the press over
  to the canvas, so the drag duplicates the text (or its container)
- the handed-over press always moves what was edited, never resize
  handles or an arrow's points, midpoint or label beneath the editor
- on drop, the duplicate is edited with all of its text selected (a list
  item's text only, as when alt-dragged on the canvas)

Claude Opus 5.5 (xhigh)

* fix(editor): no arrow hover highlights while editing its label

- starting to edit text clears the hover state of the arrow's editor
  (kept up for the submit), so a midpoint hovered before the double-click
  doesn't stay highlighted
- the arrow's hover affordances don't apply while editing text

Claude Opus 5.5 (xhigh)

* fix(editor): don't drop arrow hover updates on the same pointer move

- the hovered point, midpoint and focus point were each set from
  `this.state`, so when one move changed several of them (e.g. from the
  midpoint straight onto an endpoint), only the last update survived

Claude Opus 5.5 (xhigh)
2026-10-01 16:39:40 +02:00
David Luzar 9ba66ed9b5 feat(editor): auto increment numbers/lists on duplicate (#12189)
* feat(editor): auto increment numbers/lists on duplicate

- duplicating a text or a label (shape, arrow, sticky note) that starts with a list marker advances it: `1.` `1)` `(1)` `[1]`, `a.` `a)` `(a)` (`a`–`h`, then roman numerals `i`–`xcix`), and lone numbers (`1`)
- markers must be followed by whitespace (`1.5`, `e.g.` aren't lists); whole lists are left as they are
- numbers count up to 42, letters up to `i`
- only if nothing but list items is duplicated (a label goes with its container); several items only if they're just markers (`1.` `2.`), continuing from the highest of them (`1.`, `3.`, `5.` -> `6.`, `7.`, `8.`)
- the increment is a separate undo step after the duplication; alt-drag shows it from the start of the drag

Opus 5.5 (1M context), xhigh

* feat(editor): edit the text of an alt-duplicated list item

- on alt-drag drop, a single list item with text after its marker enters the text editor with that text selected (`2. |foo|`)
- not when duplicated along with other elements, nor when the drag doesn't end with a genuine pointerup (pointercancel, missing-pointerup cleanup)
- `textWysiwyg` / `startTextEditing` take an `initialSelection`

Opus 5.5 (1M context), xhigh
2026-10-01 15:08:33 +02:00
David Luzar 1919728724 fix(editor): reach text containers below transparent ones (#12210)
The text tool (hover and click), and a double-click with nothing
selected, took the top-most shape whose bounds held the pointer. A
transparent shape stacked above a nested one kept the inner one out of
reach at its center, and an arrow below a transparent shape couldn't get
a label.

- only a filled element or an image (the rule arrow binding uses, now
  exported as isOpaqueForBinding) or an arrow ends the search
- of the containers found, the innermost one whose center is at the
  pointer wins, else the top-most as before
- an arrow counts only where its path is hit, not anywhere in its bounds
- a frame's children aren't hit outside the frame, where they're clipped
  (App.isClippedByFrameAt, shared with getElementsAtPosition)

Claude Opus 5.5 (1M), xhigh effort
2026-09-30 23:26:42 +02:00