Last modified: 2014-10-16 13:56:36 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T49885, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 47885 - Thread title containing "</div>" destroys entire page with $wgUseTidy = true
Thread title containing "</div>" destroys entire page with $wgUseTidy = true
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: High major (vote)
: ---
Assigned To: Nobody - You can work on this!
https://www.mediawiki.org/wiki/Thread...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-30 16:43 UTC by Krinkle
Modified: 2014-10-16 13:56 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
Screenshot of LQT thread with </div> in title (513.91 KB, image/png)
2013-04-30 16:43 UTC, Krinkle
Details

Description Krinkle 2013-04-30 16:43:28 UTC
Created attachment 12211 [details]
Screenshot of LQT thread with </div> in title

Should be treated the same as regular page titles: Escape everything.


Or, if we want to keep wikitext parsing (e.g. for wikilinks, sometimes done in section headings), then parse as inline block (not allowing any block level elements like <div> or <table>) and make sure open/close tags match (run Tidy).
Comment 1 Krinkle 2013-04-30 21:01:53 UTC
@Krenair: You change the summary to include "with wgUseTidy = true;" Are you saying that when Tidy is disabled this bug does not happen?

Seems more like the opposite?
Comment 2 Alex Monk 2013-04-30 21:52:10 UTC
(In reply to comment #1)
> @Krenair: You change the summary to include "with wgUseTidy = true;" Are you
> saying that when Tidy is disabled this bug does not happen?


Yes. I have to add that to my configuration to replicate this bug.
Comment 3 Nemo 2013-08-30 05:48:31 UTC
This is one of the many places with poor or inconsistent escaping in LQT.
Comment 4 Helder 2014-10-16 13:56:36 UTC
A similar problem in a topic named "Handling <pre><ref></pre> with trailing slash does not work correctly":
https://www.mediawiki.org/wiki/Thread:VisualEditor/Feedback/Handling_ref_with_trailing_slash_does_not_work_correctly

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links