Content
Updated by Wieland Lindenthal about 1 year ago
**As** a work package description editor
**I want to** be able to have better UX working with the editor
**so that** I am more productive with it and I do not leave OpenProject to edit work package descriptions.
**Acceptance criteria**
* (see video) After clicking `Switch to Markdown source editor` text area has the same behavior as in WYSIWIG mode(presence of horizontal/vertical scrolling and text wraps). Current behavior:
* WYSIWIG text area has no scrolling, but Markdown text area has horizontal and vertical scrolling
* WYSIWIG text area has text wrapped while Markdown has text unwrapped
* (see video) After clicking `Switch to Markdown source editor` cursor is placed at the same location as it was in WYSIWIG mode. Current behavior: the last location is not saved. Therefore, user has to find last editing place manually.
* [https://www.openproject.org/docs/user-guide/wysiwyg/](https://www.openproject.org/docs/user-guide/wysiwyg/) `?` is extracted from the top bar and more obvious for user to find. Currently it is in the line with buttons that are related to text editing. Therefore it is not expected to be there and "has to be found":<img class="image_resized op-uc-image op-uc-image_inline" style="width:412px;" src="/api/v3/attachments/196070/content">
* (see video) Extra line breaks are not removed in WYSIWIG mode after save. It contradicts with WYSIWIG concept of "What you see is what you get".
* (see video) In Markdown mode last line should not jump on editing.
* In case the description is quite big the it `Save` and `Discard` buttons should be more accessible. Then user do not need to scroll down to get to them. For example they could be put to the right of the description editing area top bar:<img class="image_resized op-uc-image op-uc-image_inline" style="width:412px;" src="/api/v3/attachments/196044/content">
**I want to** be able to have better UX working with the editor
**so that** I am more productive with it and I do not leave OpenProject to edit work package descriptions.
**Acceptance criteria**
* (see video) After clicking `Switch to Markdown source editor` text area has the same behavior as in WYSIWIG mode(presence of horizontal/vertical scrolling and text wraps). Current behavior:
* WYSIWIG text area has no scrolling, but Markdown text area has horizontal and vertical scrolling
* WYSIWIG text area has text wrapped while Markdown has text unwrapped
* (see video) After clicking `Switch to Markdown source editor` cursor is placed at the same location as it was in WYSIWIG mode. Current behavior: the last location is not saved. Therefore, user has to find last editing place manually.
* [https://www.openproject.org/docs/user-guide/wysiwyg/](https://www.openproject.org/docs/user-guide/wysiwyg/) `?` is extracted from the top bar and more obvious for user to find. Currently it is in the line with buttons that are related to text editing. Therefore it is not expected to be there and "has to be found":<img class="image_resized op-uc-image op-uc-image_inline" style="width:412px;" src="/api/v3/attachments/196070/content">
* (see video) Extra line breaks are not removed in WYSIWIG mode after save. It contradicts with WYSIWIG concept of "What you see is what you get".
* (see video) In Markdown mode last line should not jump on editing.
* In case the description is quite big the