You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
<#2663 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAATZ3LV7G2CMWWUXIYMXCDTGMKPFANCNFSM42ENCCEA>
.
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
The text was updated successfully, but these errors were encountered: