A damaged .ai can give a gradient mesh whose outline is enormous but finite.
draw_mesh_raster flattened that whole outline in device pixels (grown_outline),
and kurbo's flatten then asked for more segments than memory holds: a
"capacity overflow" panic (seen in import_fuzz's ai_written_meshes_never_panic).
An outline wider or taller than 2^24 device pixels now goes to the per-quad
drawing path the function already falls back to.
With no panels docked on the left and a toolbar made with New Toolbar docked there, a drop on
the canvas's left edge docks Tools at the window's edge, left of the toolbar's lane. The strip
that lit up during the move was the canvas's edge, right of the lane. The window's edge now
lights up instead.
The window.toolsBesideCanvas params text, docs/control-protocol.md, docs/target-app-parity.md and
the UiState doc comment now say that a drop with no panels docked on the left, or in the column
both edges share beside panels collapsed to icons, leaves Window › Toolbars › Keep Tools Beside
the Canvas as it is. ROADMAP's progress log gets a line for the changed drop rule.
The test of a release where the move started now presses on the title bar, moves past the drag
threshold so the move starts, and releases within the travel limit over the canvas's edge; it
fails without that limit.
A third quick click on a swatch counts as a triple click, and so does
each quick click after it. Those clicks still applied the swatch, so a
triple click on a pattern swatch opened pattern editing and then
painted the tile art with the pattern itself. Only the first click of
a run of quick clicks now applies and selects the swatch.
The test now sends four quick clicks and gives the art a solid fill in
each view, so the list view's first click is checked on its own.
A floating Tools panel dropped on the canvas's left edge, right of panels
docked on the left, stayed floating unless Window > Toolbars > Keep Tools
Beside the Canvas was on. The canvas's left edge is now always a target:
a drop there docks Tools beside the canvas and turns the setting on, and a
drop on the window's left edge docks it there and turns the setting off,
so the menu item's check mark shows where Tools is.
This changes one existing behavior: with the setting on and panels docked
on the left, a drop on the window's left edge used to dock Tools beside the
canvas and keep the setting on. It now docks Tools at the window's edge and
turns the setting off.
With no panels docked on the left, both edges put Tools in the same place
(left of any toolbars made with New Toolbar docked there), so a drop on
either docks it where the setting puts it and leaves the setting as it is.
So does a drop in the column both edges share when left-side panels are
collapsed to icons narrower than the window's edge strip. A release in the
frame right after Tools floats out of its place at the window's edge skips
the canvas-edge strip, which that frame laid out right of the docked panel.
Part of #7837
Running a script or a plug-in now ends the spot color base's link, as a
batch step already did, so a script that deletes the spot color and makes
another of the same name does not make the new one the base. Commands that
only list scripts or plug-ins keep the link.
While the link waits for an Undo, the color it captures before a command is
the one the guide shows, not that of a new spot color of the same name.