Last modified: 2012-08-23 19:04:12 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 9661 - Tidy shouldn't reopen inline tags after the end of a block
Tidy shouldn't reopen inline tags after the end of a block
Status: NEW
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: tidy
  Show dependency treegraph
Reported: 2007-04-22 14:35 UTC by Cesar Eduardo Barros
Modified: 2012-08-23 19:04 UTC (History)
1 user (show)

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


Description Cesar Eduardo Barros 2007-04-22 14:35:25 UTC
There was a missing </small> in a users's signature in the [[Template
talk:High-traffic]] page. The software (I'm guessing it's HTML tidy) correctly
closed the missing tag, but then incorrectly reopened it on every block for
several sections (starting at the "Comments" section). It only ended (in the
"Category" section) after finding a matching <small>...</small> pair. It should
not reopen a tag on the next block after closing it on a block's closing tag.
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-04-22 20:22:17 UTC
This is deliberate.  The idea is that

This is lots of text.

I expect it all to be small.

should work, so that HTML neophytes need not be troubled by block vs. inline
tags (which is very unintuitive: why *shouldn't* you be able to declare multiple
paragraphs emphasized all in one go?).  It will occasionally have weird effects
like this, and more subtle ones when it comes to CSS or JavaScript (because the
nesting won't be as intended).  Possibly we should disable it, if possible, but
keep in mind that this will undoubtedly break a large number of pages.
Comment 2 Cesar Eduardo Barros 2007-04-23 15:05:21 UTC
I don't think changing it would affect many pages; every time I've seen where
the intention was to change the size of text for more than one block element, it
was done via CSS (often in a template).

Even if it's the case, it would be better to explicitly do the closing/reopening
in the parser, instead of letting tidy do the work, since with tidy there's a
greater chance of it spilling (sometimes even into the interface).

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