Repository navigation
feat(editor): ease transient UI surfaces - #93
Merged
Merged
Conversation
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.
3 of 8 tasks
2 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
Affected areas
This is editor chrome only. No store, document, history, serialization, export or MCP module changes, so those paths need no new capability.
Acceptance criteria
apps/web/src/motion.css.docs/editor-motion.md.motion.css.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: passedcorepack pnpm run check: passedcorepack pnpm run build: passed (existing chunk-size warning only)corepack pnpm run changeset:status --since=origin/main: passed, patch for@open-cavas/webgit diff --check: passedReal 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 updatedDESIGN.md,README.md,docs/verification.mdand 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