bflatasticandClaude Opus 5.5 accfec7146 Fix #359: web drops land in the document they were dropped on ...

The web reads dropped files asynchronously, and the place inbox only kept
the drop point, so a file dropped on document A was placed into whatever
document was active when its bytes arrived. A drop on a canvas now carries
place::DropAt (the document's uid, the point, embed), and drop_files makes
that document active again before placing; when it has closed meanwhile,
nothing is placed and the status bar says so. The native drop path is
synchronous and goes through the same code, so it is unchanged in effect.

Test: a drop pending while another document opens lands in the first one
at the drop point; one whose document closes is not placed anywhere.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2026-10-08 05:28:50 +07:00

..

vectorcraft

Fix #306: render on the power-saving GPU by default, with a preference for the discrete one

2026-10-07 21:10:17 +07:00

vectorcraft-cli

mcp: sweep protocol surface over stdio against the binary

2026-10-07 16:39:06 +03:00

vectorcraft-web

Fix #359: web drops land in the document they were dropped on

2026-10-08 05:28:50 +07:00