#### Steps to reproduce 1. I saved (posted) a comment on GitHub (or GitLab). 2. I modified that comment. 3. I saved (posted) that (modified) comment. 4. I entered the edit mode again. #### Actual results Instead of displaying the updated comment content, the previous content is displayed. Refreshing the page once usually remediates this, and refreshing it 2 to 3 times always does. I *presume* that this is due to caching, considering that input form content is usually cached, except upon manual refresh. I would have considered this to be a fault with either GitHub or GitLab, had it not occurred on both. It occurs on GitHub incredibly frequently, in comparison to GitLab. #### Expected results The new content should be displayed.
Bug 1937425 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
#### Steps to reproduce 1. I saved (posted) a comment on GitHub (or GitLab). 1. I modified that comment. 1. I saved (posted) that (modified) comment. 1. I entered the edit mode again. #### Actual results Instead of displaying the updated comment content, the previous content is displayed. Refreshing the page once usually remediates this, and refreshing it 2 to 3 times always does. I *presume* that this is due to caching, considering that input form content is usually cached, except upon manual refresh. I would have considered this to be a fault with either GitHub or GitLab, had it not occurred on both. It occurs on GitHub incredibly frequently, in comparison to GitLab. #### Expected results The new content should be displayed.
#### How To Reproduce 1. I saved (posted) a comment on GitHub (or GitLab). 1. I modified that comment. 1. I saved (posted) that (modified) comment. 1. I entered the edit mode again. #### Actual Result Instead of displaying the updated comment content, the previous content is displayed. Refreshing the page once usually remediates this, and refreshing it 2 to 3 times always does. I *presume* that this is due to caching, considering that input form content is usually cached, except upon manual refresh. I would have considered this to be a fault with either GitHub or GitLab, had it not occurred on both. It occurs on GitHub incredibly frequently, in comparison to GitLab. #### Expected Result The new content should be displayed. #### My Environment The latest version reproduced on is `145.0.1`.