Comment section will not clean after posting a comment !

[mahyar-amiri]

When I post a comment, the comment section will not clean and I can see the text in the comment teaxtarea. There might be a bug in resetCreateForms function in comment/static/js/comment.js. Surprisingly, The resetCreateForms function cleans Reply Section Textarea but not Reply Section Textarea.

[ogurec-ogurec]

@mahyar-amiri hi, tell, did you somehow solve this problem?

[ChathuraGH]

@mahyar-amiri

function cleans Reply Section Textarea but not Reply Section Textarea.

Isn't that the same thing?
Help me understand your problem.
Tell us how to reproduce the problem.

[ogurec-ogurec]

@ChathuraGH I'll try to show a reproduction:

1. Write any comment in the input comment;
2. Click the "Comment" button;
3. Comment is published, but:
   4. Comment text field is not clearing of text (comment)
4. Also, the contents of the input are duplicated in the response input;
5. If you just reply to the comment, there is no such problem;

DAB version 2.8.0

[ogurec-ogurec]

@ChathuraGH what do you think?

[ChathuraGH]

On latest Google Chrome Browser,

On Example site,
On "https://rmustafa.pythonanywhere.com/test-post/" It works.

screen-capture.webm

On old django-comments-dab==1.6.7
it works.

screen-capture.1.webm

What is your browser, browser version?

[ChathuraGH]

What was the error? did you solve it?

[ogurec-ogurec]

@ChathuraGH not solved, the error is that after sending a comment, the input of the comment and the input of the response are not cleared. I tried it in another browser, same thing (

I suspect it’s not the browser

If you write a response, the form is cleared, but if you write a comment, then no

DAB version 2.8.0

[ChathuraGH]

On latest Google Chrome Browser,

On Example site, On "https://rmustafa.pythonanywhere.com/test-post/" It works.

screen-capture.webm
On old django-comments-dab==1.6.7 it works.

screen-capture.1.webm
What is your browser, browser version?

But if you look at my screen recordings above ., you can see it working properly. I couldn't reproduce your problem with v=2.8.1 or 1.6.7 . (I didn't try 2.8.0).