Document formatting #371

Closed
opened 2026-02-04 19:09:26 +03:00 by OVERLORD · 3 comments
Owner

Originally created by @vladime on GitHub (Jul 11, 2017).

For Bug Reports

  • BookStack Version: 0.17.0
  • PHP Version: PHP7
  • MySQL Version: 5.7.12
Expected Behaviour
  1. There is a "document" in markdown formatting.
  2. Switching Page editor to "WYSIWYG".
  3. Editing "document" in "WYSIWYG" mode
  4. Switching Page editor back to "Markdown".
  5. "document" formatting is in HTML format full with HTML tags. Markdown formatting is gone forever.
Actual Behaviour

Formatting of a document (page) should correspond the Page editor after switch.

Originally created by @vladime on GitHub (Jul 11, 2017). ### For Bug Reports * BookStack Version: 0.17.0 * PHP Version: PHP7 * MySQL Version: 5.7.12 ##### Expected Behaviour 1. There is a "document" in markdown formatting. 2. Switching Page editor to "WYSIWYG". 3. Editing "document" in "WYSIWYG" mode 4. Switching Page editor back to "Markdown". 5. "document" formatting is in HTML format full with HTML tags. Markdown formatting is gone forever. ##### Actual Behaviour Formatting of a document (page) should correspond the Page editor after switch.
Author
Owner

@lommes commented on GitHub (Jul 11, 2017):

I'm not sure if this is really necessary since markdown is completly fine with including any valid HTML. There are some things you just can't do with markdown like adding classes to image tags. These customizations would be completly lost and, other than your example, has influence on the rendered output.

@lommes commented on GitHub (Jul 11, 2017): I'm not sure if this is really necessary since markdown is completly fine with including any valid HTML. There are some things you just can't do with markdown like adding classes to image tags. These customizations would be completly lost and, other than your example, has influence on the rendered output.
Author
Owner

@ssddanbrown commented on GitHub (Jul 11, 2017):

@vladime Hi there and thanks for submitting an issue.

@lommes is correct in the fact that this is technically fine and also necessary to prevent formatting loss.

An issue for pretty much the same thing is already open under #369 so I will close this issue. Feel free to contribute to the discussion there.

@ssddanbrown commented on GitHub (Jul 11, 2017): @vladime Hi there and thanks for submitting an issue. @lommes is correct in the fact that this is technically fine and also necessary to prevent formatting loss. An issue for pretty much the same thing is already open under #369 so I will close this issue. Feel free to contribute to the discussion there.
Author
Owner

@vladime commented on GitHub (Jul 12, 2017):

Thank you guys for the quick response.
@lommes I get you point. It is just for some people WYSIWYG is easier to use and for some Markdown. And since there is no personal setting for default Page editor format switching feature would make sense.
@ssddanbrown thanks for the link. Will go there.

@vladime commented on GitHub (Jul 12, 2017): Thank you guys for the quick response. @lommes I get you point. It is just for some people WYSIWYG is easier to use and for some Markdown. And since there is no personal setting for default Page editor format switching feature would make sense. @ssddanbrown thanks for the link. Will go there.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/BookStack#371