Last modified: 2005-03-05 02:04:28 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 T3634, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 1634 - invalid XHTML on VfD page (en.wikipedia)
invalid XHTML on VfD page (en.wikipedia)
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
PC All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: html
  Show dependency treegraph
Reported: 2005-03-04 13:31 UTC by Alex Brooks
Modified: 2005-03-05 02:04 UTC (History)
0 users

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


Description Alex Brooks 2005-03-04 13:31:51 UTC

The Vfd page has many of the following errors:

Line (take your pick), column 26: ID "vfd" already defined

<div class="metadata" id="vfd" style=

An "id" is a unique identifier. Each time this attribute is used in a document
it must have a different value. If you are using this attribute as a hock for
style sheets it may be more appropriate to use classes (which group elements)
than id (which are used to identify exactly one element).
Comment 1 Rowan Collins [IMSoP] 2005-03-05 02:04:28 UTC
It turns out this element was being set in, which is used in archived VfD
discussions. I'm not sure why it was there, but it was breaking because multiple
archived discussions were being included on one page, thus creating multiple
divs with the same id.

Thinking it would probably do no harm, I removed the offending attribute;
unfortunately, the template was inserted with {{subst:}}, so the changes haven't
had an immediate effect, but future uses of it shouldn't trigger the problem.

Of course, if there *was* a good reason it was there, someone may add it back
in, in which case we may just have to put up with the errors for the sake of
that purpose.

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