[BUG] Using the "increase git diff context lines buttons" hides draft comment replies, scarily #163214

bryce-carson · 2025-06-18T06:06:35Z

bryce-carson
Jun 18, 2025

Select Topic Area

Bug Report

Body

Letter

GitHub,

When drafting a reply to a comment on lines of a commit, if the user presses the upper or lower git diff context button to increase the number of context lines for the diff the draft response will disappear. Once the user clicks on some part of the comment interface again the drafted reply will reappear.

I found this behaviour disconcerting, and was upset, thinking I had lost my draft. Thankfully I did not. I though to bring this visual behaviour to your attention so that it may be corrected.

Regards,

Bryce.

Steps to reproduce

Navigate to a comment on lines of a commit
Draft a reply to any comment
Press the upper or lower buttons used to acquire more context lines for the same git diff chunk
Observe draft is no longer visible
Click on the same comment interface; clicking in the reply area should be sufficient.

A marked up screenshot is provided for clarity.

imramkrishna · 2025-06-19T03:53:31Z

imramkrishna
Jun 19, 2025

Where to Report This Bug
Primary option:

GitHub Support: support.github.com
Category: "Bug report"
Product: "GitHub.com"

Alternative option:

GitHub Community Discussions: github.com/orgs/community/discussions
Use the "General" category and tag it as a bug report

Enhanced Bug Report Template
Here's your report formatted for maximum clarity:
Subject: Draft comment disappears temporarily when expanding git diff context
Description:
Bug Summary:
When drafting a reply to a comment on specific lines of a commit, the draft response temporarily disappears if the user clicks the git diff context buttons (+ or -) to expand/collapse context lines.

Steps to Reproduce:

Navigate to a commit with a comment on specific lines
Click "Reply" to start drafting a response
Type some text in the draft reply
Click the git diff context expand/collapse buttons (+ or -)
Observe that the draft text disappears from view

Expected Behavior:
Draft text should remain visible when expanding/collapsing diff context.

Actual Behavior:
Draft text disappears temporarily but reappears when clicking back on the comment interface.

Impact:
This creates a confusing user experience where users think they've lost their work (even though the draft is actually preserved).

Browser/Environment:
[Include your browser, version, and OS]

Additional Notes:
The draft is actually preserved and reappears when interacting with the comment interface again, but the visual behavior is disconcerting.
Why This is a Good Bug Report
Your report includes:

✅ Clear reproduction steps
✅ Expected vs actual behavior
✅ Impact assessment
✅ Confirmation that data isn't actually lost

Additional Info to Include
Consider adding:

Browser and version
Operating system
Whether this happens consistently
Screenshots or screen recording if possible

This is exactly the kind of UX issue that GitHub's team would want to know about and fix.

1 reply

bryce-carson Jun 19, 2025
Author

Thanks for that formatting and the suggestions for bug reporting. I believed this was the correct place, and maybe it is (if I follow the alternate bug report option); I think I'd just need to tag this as a bug report, no?

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

GitHub Community

[BUG] Using the "increase git diff context lines buttons" hides draft comment replies, scarily #163214

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 1 comment 1 reply

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

GitHub Community

[BUG] Using the "increase git diff context lines buttons" hides draft comment replies, scarily #163214

Uh oh!

Uh oh!

bryce-carson Jun 18, 2025

Select Topic Area

Body

Letter

Steps to reproduce

Replies: 1 comment · 1 reply

Uh oh!

imramkrishna Jun 19, 2025

Uh oh!

bryce-carson Jun 19, 2025 Author

bryce-carson
Jun 18, 2025

Replies: 1 comment 1 reply

imramkrishna
Jun 19, 2025

bryce-carson Jun 19, 2025
Author