After saving the content of the post, it renders for approximately 4 ms in the rendered post, before a loading circle appears for 2 ms, and it’s gone:
Solutions
If it rendering in the previewer is accidental, and it being cleansed from the rendered post is deliberate because of security concerns that I’m unaware of, could you not at least just replace <button> with <button disabled>?
I ask because I see frequent misuse of <code> and <kbd> where <button> would be semantic, especially in tutorials and reproduction steps.
You see the button in preview because it’s a side effect of the tag that is allowed here.
However, the disabled attribute is ignored because it is not defined.
I did not check how the allowed list is parsed; I wonder if it’s the expected behavior. . Currently, it seems the tag is allowed regardless of the attributes. I would have expected that the button is not rendered if you are not using exactly, for example, <button class="alt-text-edit-ok btn btn-primary">.
You can make a plugin to allow <button> on post render. Let me know if you need assistance.
@Arkshine, I am thankful. However, I’m not an instance operator. I’ve merely noticed this when formulating content.
This is one of many instances in which the HTML5 and CSS3 representations in the previewer differ from the eventual render, which means that writing content for Discourse can be difficult. This is especially so when edits have been disabled or limited to a very small timeframe, instance-wide.
Unfortunately, you can’t make settings in this situation, so if you want to add another tag, you will need to fork my repository and add it yourself here.
@Arkshine, can that not be upstreamed? I ask because this affects every instance I use, and asking all of them to incorporate a patch for something so trivial to them would probably be infeasible.
Usually, I’d make an issue for something like this on the relevant GitHub repository, but the issue section is disabled for Discourse’s.
. Currently, it seems the tag is allowed regardless of the attributes. I would have expected that the button is not rendered if you are not using exactly, for example, 