Last modified: 2007-01-17 20:57:32 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 T8171, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 6171 - With $wgUseTidy=false, </td> and </tr> is output as text.
With $wgUseTidy=false, </td> and </tr> is output as text.
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
1.7.x
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
http://testwiki.wegge.dk/index.php/St...
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2006-06-02 14:24 UTC by Anders Wegge Jakobsen
Modified: 2007-01-17 20:57 UTC (History)
0 users

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

Attachments
Better handling of tags with optional close tags (1.77 KB, patch)
2006-06-02 16:12 UTC, Anders Wegge Jakobsen 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Anders Wegge Jakobsen 2006-06-02 14:24:47 UTC 
The URL points to a default installation of SVN HEAD. As can be seen, </td> is
translateted to &lt;/td&gt;, instead of being put into the html as normal close
tags. The only happens when $wgUseTidy is false.

Compare to the same text in my dawiki sandbox:
http://da.wikipedia.org/wiki/Bruger:Wegge/Sandkassen/Strange_things_when_%24wgUseTidy%3Dfalse
Comment 1 Anders Wegge Jakobsen 2006-06-02 16:12:22 UTC 
Created attachment 1878 [details]
Better handling of tags with optional close tags

Push optionally-closed tags on the parser stack, and skip them during unwind,
if no close tags are found.
Comment 2 Brion Vibber 2006-06-02 18:37:01 UTC 
Cannot reproduce problem at the given URL.
Comment 3 Anders Wegge Jakobsen 2006-06-02 21:19:18 UTC 
No, not after i fixed it on my test installation. I still need someone to take a
look at the patch though.
Comment 4 Anders Wegge Jakobsen 2006-06-03 00:03:29 UTC 
Fixed in SVN. Added a testcase to the parser test, demonstrating that the
sanitizer still have a problem with optional end tags.
Comment 5 Antoine "hashar" Musso (WMF) 2007-01-17 20:57:32 UTC 
Fixed in r19400. We now automaticly close tags.

Parser tests seems fine:

<snip>
1 previously failing test(s) now PASSING! :)
  * TODO: Parsing optional HTML elements (Bug 6171)
18 still FAILING test(s) :(
<snip>
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links