Markdown wraps words in table with long columns #2179

New Issue

OVERLORD · 2026-02-05T03:12:55+03:00

OVERLORD commented

2026-02-05 03:12:55 +03:00

Originally created by @nycterent on GitHub (Mar 31, 2021).

Source markdown:

Preview:

Result:

So you can see - the result has split words, which is unexpected for markdown, I would expect the same result as in Preview

Originally created by @nycterent on GitHub (Mar 31, 2021). Source markdown: ![image](https://user-images.githubusercontent.com/81133/113136968-a470bc00-922c-11eb-9f37-60c3c891e09f.png) Preview: ![image](https://user-images.githubusercontent.com/81133/113137036-b3f00500-922c-11eb-95a1-e3233c89c5e4.png) Result: ![image](https://user-images.githubusercontent.com/81133/113137073-bd796d00-922c-11eb-84d0-e54e6ab2de5e.png) So you can see - the result has split words, which is unexpected for markdown, I would expect the same result as in Preview

OVERLORD added the 🐛 Bug 🎨 Design 💻 Front-End labels 2026-02-05 03:12:55 +03:00

OVERLORD commented

2026-02-05 03:13:01 +03:00

@ssddanbrown commented on GitHub (Mar 31, 2021):

Thanks for raising @nycterent.

The final display is really dependent on the styling rules of the table on the page, I don't think there's really any expectations of the behavior for markdown itself.

I'll keep this open with the resolution being aligning the behavior across the preview and end-result, But it might be the case we standardise on the shown result rather than the preview.

For these kind of details, such as long keys you'll need to copy, reformatting the structure to use a code block may suit your needs better.

@ssddanbrown commented on GitHub (Mar 31, 2021): Thanks for raising @nycterent. The final display is really dependent on the styling rules of the table on the page, I don't think there's really any expectations of the behavior for markdown itself. I'll keep this open with the resolution being aligning the behavior across the preview and end-result, But it might be the case we standardise on the shown result rather than the preview. For these kind of details, such as long keys you'll need to copy, reformatting the structure to use a code block may suit your needs better.

OVERLORD commented

2026-02-05 03:13:05 +03:00

@nycterent commented on GitHub (Mar 31, 2021):

probably i am doing something wrong, but using ` or ``` does not solve the
problem - the words are still split

On Wed, 31 Mar 2021 at 15:45, Dan Brown @.***> wrote:

Thanks for raising @nycterent https://github.com/nycterent.

The final display is really dependent on the styling rules of the table on
the page, I don't think there's really any expectations of the behavior for
markdown itself.

I'll keep this open with the resolution being aligning the behavior across
the preview and end-result, But it might be the case we standardise on the
shown result rather than the preview.

For these kind of details, such as long keys you'll need to copy,
reformatting the structure to use a code block may suit your needs better.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/BookStackApp/BookStack/issues/2663#issuecomment-811039349,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAATZ3LV7G2CMWWUXIYMXCDTGMKPFANCNFSM42ENCCEA
.

@nycterent commented on GitHub (Mar 31, 2021): probably i am doing something wrong, but using ` or ``` does not solve the problem - the words are still split On Wed, 31 Mar 2021 at 15:45, Dan Brown ***@***.***> wrote: > Thanks for raising @nycterent <https://github.com/nycterent>. > > The final display is really dependent on the styling rules of the table on > the page, I don't think there's really any expectations of the behavior for > markdown itself. > > I'll keep this open with the resolution being aligning the behavior across > the preview and end-result, But it might be the case we standardise on the > shown result rather than the preview. > > For these kind of details, such as long keys you'll need to copy, > reformatting the structure to use a code block may suit your needs better. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/BookStackApp/BookStack/issues/2663#issuecomment-811039349>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAATZ3LV7G2CMWWUXIYMXCDTGMKPFANCNFSM42ENCCEA> > . >

Sign in to join this conversation.

Branches Tags

development

l10n_development

release

v26-03

ci_fixing

codeberg-actions

lexical_may_2026

MilnerMart/development

sort_rule_text

GamerClassN7/impersonations-for-admin

Zhey-on/feature/csp-image-css-controls-6033

tortillas5/development

clauvaldez/mfaReset

llm_only

vectors

McTom234/oidc-key-algorithms

docker_env

drawio_rendering

user_permissions

ldap_host_failover

svg_image

prosemirror

captcha_example

fix/video-export

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#2179