It doesnât look like they do:
The < br > tag works though.
1 Like
oh! try it with capital âSâ? And with â<ââŠ
<Spoiler></Spoiler>
This is part of the reason having the widget really helpsâŠ
3 Likes
< > alone didnât do anything, but the capital S worked, yes.
2 Likes
Erm, whut? This is something homegrown, I guess? Couldnât find it in the HTML5 spec (or maybe Iâm too stupid to use GoogleâŠ)
<Spoiler> is not markdown, or am I missing something?
3 Likes
Could it be the reason spoilers in reviews donât work in Firefox? Thatâs the tag used for spoilers in reviews, <Spoiler>, not [spoiler].
3 Likes
Requiring a capital S is very strange. It would never have occurred to me to not use lowercase. Itâs also weird that it used <> instead of [], which is what Iâd always seen before Natively. (Thatâs also what Discourse uses by the way.)
Either way, it should be made case insensitive.
3 Likes
I mean yeah⊠thereâs nothing in the HTML spec that does a spoiler behavior? 
Agreed that it should be case insensitive. Honestly not sure if it is case sensitive, but can try when I get home
1 Like
From my own small experiment, itâs definitely case sensitive. <spoiler> didnât do anything, only <Spoiler> did.
5 Likes
If this is something you can modify, and not just a built-in limitation of the editor, typing <Spoiler> is infinitely more annoying than [spoiler] on mobile (at least on Gboard, which my devices use), and the widget doesnât always work well with longer content⊠So it would be really helpful to add the brackets one as a synonym
And as others said, the < > do misleadingly give the impression that itâs an HTML element, rather than a shortcode that adds a css class, iirc
2 Likes
unfortunately the <> are a limitation of the widget package iâm using⊠but to be frank the API does make more sense than discourseâs does. Basically, they allow certain html elements and standard markdown⊠but if you want a custom element you simply make a custom html element, similar to an XML document.
I perhaps could change the case insensitiveness, but I think the real solution here is to simply add the full widget 
5 Likes
Ahh, it is a limitation then, gotcha.
I agree that the widget is the main solution, but case sensitivity is really an unnecessary confusion and inconvenience, esp on mobile. So it would be great to have both, if possible.
2 Likes
Well granted there is nothing (apart from <summary> but thatâs a âhide detailsâ thing) but if you call it âmarkdownâ and it then turns out that itâs a HTML5 widget (or at least looks like one), then thatâs not helpful for those trying to use that.
Why donât you use a markdown widget? Some ages ago I used GitHub - markedjs/marked: A markdown parser and compiler. Built for speed. and was happy with it⊠You can just plug it in wherever, and you even get a nice menu with it and stuff.
1 Like
I can understand why it was built this way, because modern web development allows for custom HTML components, which by convention use upper case like <CustomComponent>. But usually those custom components arenât exposed directly to the end user. 
6 Likes
@brandon Hitting âissues with our serversâ againâŠ
where is this happening?
2 Likes
Found the issue, will address tomorrow!
5 Likes
So, it seems like there are a few more issues here after exploring more:
- your page number (page 4) was outside the bounds of the results and causing an error. I should handle that better obviously, but thatâs why that link is happening. Iâm not entirely sure how you generated that link without hacking the p=4.
- it seems like when you remove a âsortâ filter by clicking the âXâ on the tab, it breaks. I think this only happens for that filter from what I can tell.
If thereâs other behavior that you observe, let me know! I will try to fix those bugs within the next day or so.
4 Likes
Easy: look at all books, go to page 4, reduce the number of books (in my case by clicking on the tag filter) 
No hacking involved 
I just double-checked, and you handle it gracefully when I reduce the number of books by filtering via status (i.e. choose âAllâ, go to the last page or so, change to âReadingâ). In this case, I just get teleported to the first page, and the link is updated. Itâs just when restricting via the custom tags that it doesnât adapt the page number to the new smaller range.
BTW while youâre at it, it would be nice if I wouldnât end up on the new first page (after the reduction) but on the new last page (i.e. the page closest to the previous page number). That would logically make much more sense to me.
Is that what has been reported a number of times by others as well? That the sorting does not update if one of the filters is removed via the X? (Otherwise Iâm not sure what youâre referring to as âit breaksâ).
Sure, thanks! 
6 Likes
