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
If you are reporting a bug or requesting support, start here:
Bug or support request summary
I am using the storybook/notes addon. When rendering a table using markdown, I am getting a bunch of <br> elements between the proceeding element and the table. This is causing the table to display much farther down the page than intended.
I don't know if this is from something in Notes or a bug in marked.
Steps to reproduce
We are using Notes to display the README.md file associated with a component.
Please specify which version of Storybook and optionally any affected addons that you're running
Hey @rapheld, I looked into it and it is caused by Storybook, specifically here: https://github.com/storybooks/storybook/blob/master/addons/notes/src/register.js#L48. The table creates a string of HTML elements, with each of them proceeded by a \n. All of them thus get extended with a <br />, causing the issue that you're reporting. Unfortunately, there is no negative lookbehind in js, so we will have to find another decent solution.
If you are reporting a bug or requesting support, start here:
Bug or support request summary
I am using the
storybook/notes
addon. When rendering a table using markdown, I am getting a bunch of<br>
elements between the proceeding element and the table. This is causing the table to display much farther down the page than intended.I don't know if this is from something in
Notes
or a bug inmarked
.Steps to reproduce
We are using
Notes
to display theREADME.md
file associated with a component.Please specify which version of Storybook and optionally any affected addons that you're running
@storybook/react
3.4.3@storybook/addon-notes
3.4.3Affected platforms
Screenshots / Screencast / Code Snippets (Optional)
Markdown
Rendered page
DOM
The text was updated successfully, but these errors were encountered: