https://bugzilla.wikimedia.org/show_bug.cgi?id=55825
--- Comment #7 from djr...@riseup.net ---
(In reply to comment #6)
> No different from if you were incorrectly using <ref>, <pre>, <nowiki> and
> other hacks of html, where if you don't close tags before opening others it
> breaks. Remember that they are not true html tags. Try and put some
> expanding
> templates inside some tags and they fail miserably, which is why we have
> magic
> words like {{#tag:...}} to make things function properly, the issue is as
> stated above, we are not properly nesting open and closing of tags.
>
> Poem is just a formatting, nothing more, it neither shows starts nor ends of
> poems. You can correctly format poems by closing the poem tag inside
> <noinclude>. Alterntiavely, if you want correctly formatted then you can
> format
> without using poem and just use <br />
>
> The issue is also due to the ProofreadPage extension and how we stick pages
> together, and have the header and footer components on the one page where it
> is
> just a javascript presentation, rather than three separate components. It is
> all less than perfect. C'est la vie.
The testcase page I linked shows that this happens without ProofreadPage's
javascript effects. What you can and can't do by avoiding using <poem> is a
mixed bag. There's a few tests on the linked test page, feel free to mess
around with these.
While I would like to emphasize the apparent issues of <poem> breaking
<noinclude>, if it's as simple as "fix issue by not using tag at all," then
please mark this bug as "won't fix." (Sorry if I come off as rude, just trying
to be brief!)
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
