Hi! I also run into this issue playing around.

One hypothetical way to solve this could be:

1. Accept children in a <slot> and listen to the slotchange event.
2. re-run the converter when that happens.

To apply the mentioned idea, registering the component as a customElement would be needed.

I mention that because having a quick look at the code I was surprised to see that the <github-md> custom element is not registered as one. Why not?

tomyo

To be frankly honest - I was looking for a solution to add Markdown support to another repo under MarketingPipeline. I thought instead of wasting time adding Markdown to future websites I might want markdown support on it'd be better to take an approach at trying to solve a way to just add it whenever needed.

Myself (being a noob in JavaScript) - grabbed a parser. Added a tag with no impression it would work - but I figured, I could try right? And it did - so I just rolled with it.

I thought it was a more than cool & useful concept - and thought it might solve someone else's problem!

But - there is obviously lot's of room for improvement on this project hence released under the GPL-3.0 license so people with more experience like yourself can give input / feedback & support that benefits all the user's of Markdown-Tag

Currently porting MarkdownTag to a WebComponent.
As of now, you can update the markdown on the fly instantly by modifying the HTML itself, or programatically using a setInput function.
My current focus is attempting to prevent XSS attacks, however my research has concluded that the only way to prevent it is programatically, as it is impossible to access the element before the DOM is rendered.

Currently porting MarkdownTag to a WebComponent. As of now, you can update the markdown on the fly instantly by modifying the HTML itself, or programatically using a setInput function. My current focus is attempting to prevent XSS attacks, however my research has concluded that the only way to prevent it is programatically, as it is impossible to access the element before the DOM is rendered.

This is out of my skill set as of right now - but dropping this here to help you.

ShowDown

       Showdown doesn't sanitize the input. This is by design since markdown relies on it to allow certain features to be correctly parsed into HTML. This, however, means XSS injection is quite possible.

Please refer to the wiki article Markdown's XSS Vulnerability (and how to mitigate it) for more information.

Marked

        Warning: Marked does not [sanitize](https://marked.js.org/#/USING_ADVANCED.md#options) the output HTML. Please use a sanitize library, like [DOMPurify](https://github.com/cure53/DOMPurify) (recommended), [sanitize-html](https://github.com/apostrophecms/sanitize-html) or [insane](https://github.com/bevacqua/insane) on the output HTML! rotating_light

The added discussion as well - I am hoping you can drop input into What would the preferred Markdown Tag be?

Tho based on your fork I think I know your input hahah! Tho would be great if we could get some more input from others before making the final decision.

Awesome work as well! ps; you have been invited to this repo if you didn't join already.

I'm using DOMPurify to sanitize the HTML, and is called on every parser before generating the HTML from the markdown.
For the input, it is required by spec to have a hiphen, so I went ahead with md-tag.
And I already joined, yes, thank you for the invitation.

I went with a very simple approach on my own, and called it mark-down, just to play with the idea mentioned above. Looks like that approach does works just fine! :)

Sharing the repo here, in case it can serve as inspiration, the same way this repo inspired me to do that one. Thanks!

@tomyo - we are actually in the process of updating with a web component if by chance you are looking for something to contribute too!

This issue has been marked as resolved.

To render changes / elements added call the function like so -

renderMarkdown()