Skip to content

feat: add configurable reply entry and regression smoke coverage#12

Merged
BobDLA merged 3 commits into
mainfrom
pr/reply-entry-regressions
Mar 20, 2026
Merged

feat: add configurable reply entry and regression smoke coverage#12
BobDLA merged 3 commits into
mainfrom
pr/reply-entry-regressions

Conversation

@BobDLA

@BobDLA BobDLA commented Mar 20, 2026

Copy link
Copy Markdown
Owner

Summary

  • add a header-level 回复主题 entry and make the floating reply FAB optional, defaulting to off
  • hide the floating FAB reliably when disabled or when the settings layer is open, and keep the reply panel aligned below the header
  • keep the header toolbar actions from collapsing into narrow vertical pills
  • extend the agent smoke library with reply-entry and toolbar-layout regression coverage while preserving the existing drawer scroll containment case

Testing

  • bash scripts/check.sh
  • bash -n scripts/agent-smoke.sh
  • bash scripts/agent-smoke.sh --cdp-port 9222 --cases AGENT-CHROME-013,AGENT-CHROME-014,AGENT-CHROME-015

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a3a087be28

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/content.js
Comment on lines +1050 to 1054
return applyAuthorFilterToViewModel({
posts,
mode: "targeted",
canAutoLoadMore: false,
hasHiddenPosts: moreAvailable

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve the targeted post when filtering to topic owner

In the targeted-preview branch, this now runs applyAuthorFilterToViewModel(...) before rendering. If a user clicks a search/user-stream result that points at /t/.../<post_number> and that post was written by someone other than the topic owner, applyAuthorFilterToViewModel() removes the only post they asked to inspect, so the drawer opens with an empty body instead of the referenced reply. The targeted path should bypass the owner filter or always retain the resolved target post.

Useful? React with 👍 / 👎.

Comment thread src/content.js
Comment on lines +1117 to +1121
posts: filteredPosts,
authorFilter: "topicOwner",
filterHiddenCount: Math.max(0, sourcePosts.length - filteredPosts.length),
filterUnavailable: false,
hasHiddenPosts: Boolean(viewModel.hasHiddenPosts) || filteredPosts.length !== sourcePosts.length

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Avoid eager full-topic loading in owner-only mode

Replacing viewModel.posts with only owner posts here changes the drawer height without changing the load-more heuristic in maybeLoadMorePosts(), which still triggers whenever the rendered content is shorter than the viewport. On long topics where the owner rarely replies, opening the drawer in authorFilter=topicOwner will keep auto-fetching /posts.json batches back-to-back until the drawer is tall enough or the stream is exhausted, effectively downloading the whole thread without any user scroll.

Useful? React with 👍 / 👎.

@BobDLA BobDLA merged commit bab107a into main Mar 20, 2026
1 check passed
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.

1 participant