Skip to content

feat(editor): ease transient UI surfaces - #93

Merged
utpalsinghdev merged 6 commits into
mainfrom
feat/editor-motion
Nov 19, 2026
Merged

utpalsinghdev merged 6 commits into
mainfrom
feat/editor-motion

Conversation

@utpalsinghdev

Copy link
Copy Markdown
Owner

Summary

Review overlays, the File and Export menus, notifications, dialogs and tooltips appeared and disappeared abruptly, so everyday editing felt less polished than it should. This adds one small set of motion tokens (160 ms ease-out entrance, 100 ms ease-in exit, opacity plus a 4 to 6 px translate) and applies it per surface, covering the Review list and composer from #92 as well as the older surfaces.

Continues #70 and supersedes it. The first commit is the original change, kept with its author and conflict-resolved against the current editor (header, File menu, Home, Review list and composer). The follow-up commits replace its animation engine with CSS transitions, add the missing surfaces, and fix the docs.

Behavior that stays intact: every action runs immediately, nothing waits for an animation, exiting content is inert and pointer-transparent, and no motion is saved to artwork, history, backups or exports.

Linked issue

Closes #66

What users will see

  • Review (list, new-comment composer, conversation) fades and slides in briefly and out slightly faster. Switching between list, draft and thread reuses the open surface and does not replay motion.
  • File and Export menus fade in and out in browsers that support the required CSS. Other browsers keep the existing instant behavior.
  • Notifications fade in and out. Help, Projects, the narrow Layers and Properties panels and hover/focus tooltips fade in; their dismissal stays immediate.
  • Closing something removes it from the pointer and keyboard at once. Escape, outside click and focus return work as before.
  • With the system reduced-motion setting on, every change is immediate, including when the setting changes mid-animation.

Affected areas

  • Editor UI, navigation, or keyboard controls
  • Document schema, migration, assets, or native backup format
  • Commands, rendering, layout, or undo/redo
  • MCP tools, targets, revisions, or capabilities
  • Saving, recovery, or concurrent editing
  • Import, export, fonts, or visual fidelity
  • Runtime, release, dependencies, or default access behavior
  • Contributor tooling or documentation

This is editor chrome only. No store, document, history, serialization, export or MCP module changes, so those paths need no new capability.

Acceptance criteria

  • Review overlays and dropdowns open and close with brief, consistent transitions. Met. Frame sampling showed Review and both menus rising in about 160 ms and falling in about 100 ms, all from the same tokens in apps/web/src/motion.css.
  • Every transient surface is audited with motion or a documented reason to stay instant. Met. See the table in docs/editor-motion.md.
  • Focus, keyboard, Escape and outside click stay correct. Met in real-input runs: Review Escape returns focus to its toggle, File opens with Enter, Tab reaches New file, Escape returns focus to the summary, an outside click closes the menu, and Help and Projects stay modal with focus restored.
  • Rapid use leaves no stale overlay or invisible target. Met. Seven to eight rapid toggles ended in the right state with at most one retained surface, reopening mid-exit reversed from the current opacity, and hit testing over an exiting surface reached the canvas.
  • Reduced motion gives immediate changes. Met, including enabling it mid-entry (opacity jumped to 1) and mid-exit (surface removed at once).
  • Only opacity and transform, no loops, blur, shimmer, pulse or spinners. Met by construction in motion.css.
  • Canvas drawing, selection, panning, typing and commands are not delayed. Met. A rectangle drew and undid with real pointer input. The change touches none of those modules.
  • No document properties, undo entries or saved animation. Met. No store, document or export file changed.
  • Desktop and narrow verification. Met at 1440 x 1000 and 390 x 844, with no horizontal overflow and Layers, Properties and Review staying mutually exclusive on narrow.

Screenshots

Not applicable. The change is motion only and settled states are unchanged.

Verification

Node 24.22.1 and pnpm 12.21.0:

  • corepack pnpm install --frozen-lockfile: passed
  • corepack pnpm run check: passed
  • corepack pnpm run build: passed (existing chunk-size warning only)
  • corepack pnpm run changeset:status --since=origin/main: passed, patch for @open-cavas/web
  • git diff --check: passed

Real browser journeys ran against the dev server in local Brave with synthetic content, sampling computed opacity per animation frame, covering Review (open, close, rapid, switch, composer Escape and Cancel cycles), File and Export, Help, Projects, notification, tooltip, narrow panels and emulated reduced motion.

Not exercised: Safari, Firefox, macOS, touch hardware, assistive technology, forced colors, a painted-frame flicker measurement, and the menu fallback in browsers without ::details-content. No new test files were added, per repository policy.

Docs and limits

Added docs/editor-motion.md (tokens, mechanism and the surface audit) and updated DESIGN.md, README.md, docs/verification.md and the web patch Changeset. Dialog and narrow-panel exits remain instant on purpose: a delayed modal close would keep a top-layer blocker, and a delayed panel close could cover the newly selected panel. The existing finite request dots and MCP creation reveal are unchanged.

🤖 Generated with Claude Code

SurfacePresence previously ran its own Web Animations timeline, copied
computed styles when interrupted and tracked reduced motion by hand. The
transition now lives in motion.css next to the shared tokens. The component
only marks a surface open or closed, makes the exiting copy inert and
unmounts it when no animation is left, so reopening, interruption and a
reduced-motion change settle through the browser. The Review surface
stays mounted across list, draft and thread content so only opening and
closing animate.
Hover and focus tooltips appeared abruptly. They now fade in with the
shared entrance token and still unmount the moment pointer or focus leaves,
so Escape and dismissal stay immediate. Reduced motion skips the fade.
Describe the shared tokens, how Review, menus and notifications retain
or transition content, and which transient surfaces animate or stay
instant and why. Align DESIGN.md, the README and the changeset with the
shipped behavior, including tooltips and the dialog and panel entrances.
Replace the carried-over verification notes with the sampled frame
timings, interruption, focus and reduced-motion results observed on this
branch, and list what was not exercised.
@utpalsinghdev
utpalsinghdev changed the base branch from feat/comment-composer to main November 19, 2026 18:47
@utpalsinghdev
utpalsinghdev merged commit 09ab167 into main Nov 19, 2026
1 check passed
@utpalsinghdev utpalsinghdev mentioned this pull request Nov 19, 2026
2 tasks done
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature Request] Add consistent easing to editor overlays, menus, and transitions

1 participant