anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[FEATURE]: Desktop standardize comment dialog trigger in File Viewer to prevent interference with text selection #8921

New Issue
Open
opened 2026-02-16 18:11:10 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:11:10 -05:00
Owner
Copy Link
Copy Source

Originally created by @fangwangme on GitHub (Feb 9, 2026).

Originally assigned to: @adamdotdevin on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Problem Description

The current interaction with the Comment dialog in the File Viewer is inconsistent and intrusive to the workflow.

  • Inconsistent Trigger: The dialog appears unpredictably—sometimes on a single click, other times on a double click.
  • Interference: This erratic behavior frequently interrupts text selection and normal file navigation.
  • UX Impact: File viewing is a core function that should take precedence. The comment feature is currently disrupting the primary reading experience for users who do not need to comment frequently.

Proposed Solution

We request to standardize the trigger event for the comment dialog to avoid conflicts with text selection.

  • Standardize Trigger: Change the default trigger to Double-Click (or a modifier key + click) to open the comment box.
  • Expected Behavior: Single-clicking should reliably function only for cursor placement and text selection, without triggering the comment UI.

Benefits

  • Smoother Workflow: Eliminates accidental interruptions during code reading and selection.
  • Better UX: Prioritizes the most common user action (viewing/selecting) over the secondary action (commenting).
Originally created by @fangwangme on GitHub (Feb 9, 2026). Originally assigned to: @adamdotdevin on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request ## Problem Description The current interaction with the Comment dialog in the File Viewer is inconsistent and intrusive to the workflow. - Inconsistent Trigger: The dialog appears unpredictably—sometimes on a single click, other times on a double click. - Interference: This erratic behavior frequently interrupts text selection and normal file navigation. - UX Impact: File viewing is a core function that should take precedence. The comment feature is currently disrupting the primary reading experience for users who do not need to comment frequently. ## Proposed Solution We request to standardize the trigger event for the comment dialog to avoid conflicts with text selection. - Standardize Trigger: Change the default trigger to Double-Click (or a modifier key + click) to open the comment box. - Expected Behavior: Single-clicking should reliably function only for cursor placement and text selection, without triggering the comment UI. ## Benefits - Smoother Workflow: Eliminates accidental interruptions during code reading and selection. - Better UX: Prioritizes the most common user action (viewing/selecting) over the secondary action (commenting).
yindo added the discussionweb labels 2026-02-16 18:11:10 -05:00
yindo commented 2026-02-16 18:11:11 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 9, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #11502: Web UI: What is the purpose of "Add comment" when clicking inside a file?

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Feb 9, 2026): This issue might be a duplicate of existing issues. Please check: - #11502: Web UI: What is the purpose of "Add comment" when clicking inside a file? Feel free to ignore if none of these address your specific case.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label discussion web
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8921
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?