Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong text after editing second comment on an issue #5581

Closed
2 of 7 tasks
thejavascriptman opened this issue Dec 22, 2018 · 0 comments · Fixed by #5608
Closed
2 of 7 tasks

Wrong text after editing second comment on an issue #5581

thejavascriptman opened this issue Dec 22, 2018 · 0 comments · Fixed by #5608
Labels
Milestone

Comments

@thejavascriptman
Copy link

Description

Steps to reproduce

  • Create new issue with any title and description
  • Create 2 comments
  • Edit and save the first comment
  • Edit the second comment

Expected behaviour

The text from the second comment gets editable and the correct text gets shown after saving the comment

Current behaviour

The text from the first comment gets pulled and no matter what you type, the text from the first comment gets saved instead of the current text

Screenshots

issue

@lunny lunny added the type/bug label Dec 23, 2018
@lunny lunny added this to the 1.6.3 milestone Dec 23, 2018
HarshitOnGitHub added a commit to HarshitOnGitHub/gitea that referenced this issue Dec 29, 2018
This commit fixes a bug that was causing text from previously edited
comment to get saved when two comments were edited one after other.
Text area with id of `#content` isn't unique on the page but it was
being treated as unique by the event handling code.

Fixes: go-gitea#5581.
jonasfranz pushed a commit that referenced this issue Dec 31, 2018
…5608)

* comments: Fix an incorrent DOM element selection.

This commit fixes a bug that was causing text from previously edited
comment to get saved when two comments were edited one after other.
Text area with id of `#content` isn't unique on the page but it was
being treated as unique by the event handling code.

Fixes: #5581.

* templates: Remove `id` from textarea in commit edit form.

An element is assigned an `id` only if it is unique for the whole page
but in this case there can be multiple textarea so it should have one.
HarshitOnGitHub added a commit to HarshitOnGitHub/gitea that referenced this issue Dec 31, 2018
…o-gitea#5608)

* comments: Fix an incorrent DOM element selection.

This commit fixes a bug that was causing text from previously edited
comment to get saved when two comments were edited one after other.
Text area with id of `#content` isn't unique on the page but it was
being treated as unique by the event handling code.

Fixes: go-gitea#5581.

* templates: Remove `id` from textarea in commit edit form.

An element is assigned an `id` only if it is unique for the whole page
but in this case there can be multiple textarea so it should have one.
techknowlogick pushed a commit that referenced this issue Dec 31, 2018
…5608) (#5615)

* comments: Fix an incorrent DOM element selection.

This commit fixes a bug that was causing text from previously edited
comment to get saved when two comments were edited one after other.
Text area with id of `#content` isn't unique on the page but it was
being treated as unique by the event handling code.

Fixes: #5581.

* templates: Remove `id` from textarea in commit edit form.

An element is assigned an `id` only if it is unique for the whole page
but in this case there can be multiple textarea so it should have one.
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants