by Rachael » Sun Jul 10, 2016 11:32 am
It's clearly a phpBB bug, then. The <div> spoiler might be a little messy, sure, but there's no reason it should be failing that epicly, either. In fact, I believe safeguards should have long been in place to prevent that.
What's happening is since the HTML-bugger-up is happening with crossing tags, the </div> from the spoiler is messing with the forum's own <div> code (which it uses by default to show every post) - so, as you'll see, the forum layout will be just fine if you switch to the subsilver2 style, since it uses tables instead of <div>s.
Honestly, with HTML5 you could just define custom tags such as <forumspoiler> and attach a style to them and be just fine. As long as <forumspoiler> is set to "display: block" in CSS, it can be used in place of <div> and it should work.
There's some more info about that here.
It's clearly a phpBB bug, then. The <div> spoiler might be a little messy, sure, but there's no reason it should be failing that epicly, either. In fact, I believe safeguards should have long been in place to prevent that.
What's happening is since the HTML-bugger-up is happening with crossing tags, the </div> from the spoiler is messing with the forum's own <div> code (which it uses by default to show every post) - so, as you'll see, the forum layout will be just fine if you switch to the subsilver2 style, since it uses tables instead of <div>s.
Honestly, with HTML5 you could just define custom tags such as <forumspoiler> and attach a style to them and be just fine. As long as <forumspoiler> is set to "display: block" in CSS, it can be used in place of <div> and it should work. [url=http://www.html5rocks.com/en/tutorials/webcomponents/customelements/]There's some more info about that here.[/url]