Redesign FwLite comments panel with responsive layout

[hahn-kev-bot]

Summary

• Refactored CommentDialog.svelte into a modular entry-editor/comments/ component tree (CommentPanel, CommentThread, CommentItem, CommentReplyInput, CommentAuthorAvatar, CommentDialog)
• Redesigned the comments panel with a responsive docked layout: full sidebar on large screens, snap-point drawer on mobile/tablet
• Added is-extra-large.svelte.ts breakpoint hook and two new CSS breakpoints to drive the responsive layout

Screenshots

thread list (desktop)

thread list (tablet)

thread list (mobile)

thread open at default drawer stop

max drawer stop

minimum drawer stop

start new thread (mobile)

start new thread (desktop)

[coderabbitai]

Warning

Review limit reached

@hahn-kev, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 57 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e7023425-228a-4aeb-bea6-0c3cedcf4b1c

📥 Commits

Reviewing files that changed from the base of the PR and between 39970cb and f0c8e72.

📒 Files selected for processing (22)

• frontend/viewer/src/css-breakpoints.ts
• frontend/viewer/src/lib/components/ui/drawer/drawer-nested.svelte
• frontend/viewer/src/lib/components/ui/drawer/drawer.svelte
• frontend/viewer/src/lib/entry-editor/CommentDialog.svelte
• frontend/viewer/src/lib/entry-editor/comments/CommentAuthorAvatar.svelte
• frontend/viewer/src/lib/entry-editor/comments/CommentDialog.svelte
• frontend/viewer/src/lib/entry-editor/comments/CommentItem.svelte
• frontend/viewer/src/lib/entry-editor/comments/CommentPanel.svelte
• frontend/viewer/src/lib/entry-editor/comments/CommentReplyInput.svelte
• frontend/viewer/src/lib/entry-editor/comments/CommentThread.svelte
• frontend/viewer/src/lib/entry-editor/comments/comment-author.ts
• frontend/viewer/src/lib/entry-editor/comments/types.ts
• frontend/viewer/src/lib/hooks/is-extra-large.svelte.ts
• frontend/viewer/src/locales/en.po
• frontend/viewer/src/locales/es.po
• frontend/viewer/src/locales/fr.po
• frontend/viewer/src/locales/id.po
• frontend/viewer/src/locales/ko.po
• frontend/viewer/src/locales/ms.po
• frontend/viewer/src/locales/sw.po
• frontend/viewer/src/locales/vi.po
• frontend/viewer/src/project/browse/EntryView.svelte

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch comment-updates

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[myieye]

It's interesting that new comments and replies have such different buttons 🤔

[hahn-kev]

Yeah, I found that semi consistent between other apps interestingly enough.

[myieye]

This is looking very good!

But, I do have a bunch of UX thoughts:

• The new comment area looks kind of disabled. There's probably a better way to make it distinct than giving it such a gray background

• Clicking "+ Add" should focus the text-area (both if the text-area is not yet visible AND if it is already visible)
• "+ Add" is the only "add button" we have that isn't "+ <thing>". Maybe it should be "+ Comment".
• Use "+ Add" to start a thread should probably just be replaced with a button that does what it's suggesting e.g. a "+ Comment" button

• Edge case (?): Use "+ Add" to start a thread is shown even when commenting is not allowed (i.e. there's no "+ Add" button. I saw this on a local only project. But maybe it applied to the viewer role too?
• Actually after using the dev-only read-only permission toggle the commenting UI seems unchanged. So, it probably needs to respect the user's role.
• The Resolve and Unresolve buttons should probably have tooltips (preferably the fancy shadcn ones not just a title attribute)
• On mobile there's the icon resolve-button in the list and a labeled resolve button when a single comment is open. Nice. Should the user be taken back to the list when they click that resolve button? Should comments become un-editable on a resolved thread? (just UI enforced?) It turns out that GDocs does this, but only for the initial comment in a thread 😆!
• Do we track a timestamp for "Comment edited"? Probably not. Saving and exposing that would be a baby step towards transparency. E.g.
  • User one writes "This is my favorite word in the dictionary"
  • User two writes "Yes mine too"
  • User one edits their comment to "My elbow is shaped like a pineapple" 🍍🙃
  • User three thinks "You both have pineapple-shaped elbows?!"
• I'd like the "add new comment" area to be decorated with my initials avatar and/or name. It's just nice to know who I'm posting as before hand 🤔. It would also make it more obvious that we have a weird bug. The UI thinks I'm Test Admin while the backend knows I'm Tim Haasdyk...Claude is currently investigating.
• I'd love to see an indicator on the comment icon-button if there are unresolved comments