Bug #51345 change in comment field reversed

Description:
After having a "comment too lang" error while forward engineering, I rephrased my comments. 

I double-clicked on the table to open its properties (the tab on the bottom of the screen, I do not know its proper name) and in its subtab "table" with a textfield "comment" (textfield1) I changed the comment in.
However, there is a second textfield (textfield2) with the comment (the one reachable via view->object descriptions), which was not updated, neither by clicking in textfield1 nor by saving. 
But clicking into textfield2, the old comment was copied into textfield1 and my changes thereby reversed.

How to repeat:
Open a table with a comment.
Change the comment in the "table"-subtab of the tables properties.
Click on the old comment in the Description-Window.

Suggested fix:
It looks to me the update wasn't propagated properly

No reversing of the change takes place when I close the bottom-area with the properties-tab of that table and reopen it by double-clicking on the table.

Many thanks for writing a bug report. Unfortunately, I am not able to follow you.

Please describe step by step how we can reproduce this.

See the screenshot: 
I use a model with already existing tables and add some characters to the comment shown in the left field [1]. So I add an "a" to the already existing "b".
Then I click into the right field [2], nothing happens (except for that it get the focus...), it still shows the old comment ("a").
Then I click into the left field, the previous entry "ab" is reversed to "a".

See the screenshot: 
I use a model with already existing tables and add some characters to the comment shown in the left field [1]. So I add an "a" to the already existing "b".
Then I click into the right field [2], nothing happens (except for that it get the focus...), it still shows the old comment ("a").
Then I click into the left field, the previous entry "ab" is reversed to "a".

screenshot of the two textfields for comments

Attachment: mysql.png (image/png, text), 23.70 KiB.

Please, check with a newer version, 5.2.17, and inform about the results.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".