Spoilers bug

[ImmortalDao]

Hi,
I 've just noticed that the spoiler function doesn't work, won't show the spoiler text, in the group's comments section.

 

[rdn]

@ImmortalDao Thanks for reporting. Will be fixed with the next update.

 

[ImmortalDao]

@rdn
The bug is still there >_>

 

[rdn]

@ImmortalDao sry, that might have slipped through the cracks. I made sure its now staged and as soon as holo pushes the new changes live, the spoiler tag will work again on group pages.

 

[BzzBzz]

To not create another thread on similar topic I'll ninja this one

Just noticed that if you put spoiler inside spoiler then second one will not open on click.

Like
[ spoiler ] 12345 [ spoiler ] 67890 [/ spoiler] [/ spoiler]

Spoiler

12345

Spoiler

67890

When you click first (spoiler) button it properly shows "12345 (spoiler)" but when you click second one then "67890" doesn't appear.

 

[DANDAN_THE_DANDAN]

If you really wanna get to the nitty gritty details,

Spoiler

quotes don't work well

within spoilers

as well.

 

[icelord]

@rdn

 

[rdn]

Yea, the current bbcode parser library is a bit older. There are definitely better ones around. Once the forum rework is tackled, the relevant libraries will be updated to whatever is the best available. Until then, a fix for this specific problem is unlikely.

 

[ShinobuOshino]

I noticed that a spoiler doesn't work inside the Biography in the user page.

If you're asking why I'd put a spoiler in a Biography, I just wanted to say that Citrus is my favorite manga and that I'm not referring to the scans as they totally change what they say making it nonsense. I wanted to put an example to show that I'm not ranting, but that would inevitably be a spoiler. The problem is that the spoiler doesn't open. (I hope the way I handled it for now is fine, I'll change it if not.)

I quickly opened Firefox's inspector on the spoiler and everything is present but the two click events that it usually has. All the other spoilers work fine so I doubt it's a problem on my side.

EDIT: I posted here instead or a new thread as this thread's name was generic and it already contained three bugs and the solved one was quite similar to this one.