Last modified: 2014-07-18 11:53:32 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 1463 - Bugzilla uses invalid markup or wrong doctype [fixed in Bugzilla 5.0]
Bugzilla uses invalid markup or wrong doctype [fixed in Bugzilla 5.0]
Status: NEW
Product: Wikimedia
Classification: Unclassified
Bugzilla (Other open bugs)
unspecified
All All
: Lowest trivial with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
: upstream
Depends on: 16777
Blocks: 4005
  Show dependency treegraph
 
Reported: 2005-02-04 11:26 UTC by Nico R.
Modified: 2014-07-18 11:53 UTC (History)
8 users (show)

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


Attachments

Description Nico R. 2005-02-04 11:26:39 UTC
See
<URL:http://validator.w3.org/check?uri=http%3A%2F%2Fbugzilla.wikipedia.org%2F&verbose=1>,
for example.
The MediaZilla pages seem to use many empty tags without closing them (e.g.
"<br>" instead of "<br/>"). There are other bugs, too.

MediaWiki makes a constant effort to use valid markup (and it works very well),
so MediaZilla should do that, too.
Comment 1 Rowan Collins [IMSoP] 2005-02-04 16:27:00 UTC
I wondered if this, like most issues with "MediaZilla" was actually an issue
with Bugzilla [http://www.bugzilla.org/] - we could really do with a prominent
explanation that "MediaZilla" is just a few cosmetic changes to someone else's
program, and >90% of problems with it are their fault not ours.

However, plugging in Mozilla's installation of Bugzilla
(http://validator.w3.org/check?uri=http%3A%2F%2Fbugzilla.mozilla.org%2F&verbose=1),
I notice that while it doesn't validate, it doesn't give an XHTML doctype
either, so doesn't have these particular errors. So I'll hold off on closing
this until someone comes along who knows what *has* been customised.
Comment 2 Nico R. 2005-11-17 12:39:51 UTC
I checked bugzilla-2.20, it has:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"

This is different from the MediaZilla setup, which has:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

Therefore, this is not a Bugzilla, but a MediaZilla bug.

Whether Bugzilla should offer an option to output XHTML instead of HTML is
another thing. If you want that, file a Bugzilla feature request if it's not
already there.
Comment 3 Chad H. 2009-07-28 15:32:08 UTC
Worth poking again after the 3.4 install is done, not worth wasting time on before that. Also not a blocker to 9025.
Comment 4 Sam Reed (reedy) 2010-01-19 20:56:07 UTC
This can be poked now ;)
Comment 5 Siebrand Mazeland 2010-02-13 00:34:57 UTC
Bulk assign Bugzilla related issues to pdhanda: current maintainer
Comment 6 Siebrand Mazeland 2010-04-22 21:06:06 UTC
Issue still valid on current Bugzilla version 3.4.5. Observed behaviour from comment 1 and comment 2 are still true.
Comment 7 Brion Vibber 2011-01-28 01:21:27 UTC
Current validation issues:

* there's no longer a doctype declaration at all -- validator's going per HTML 4.01 transitional. (Should probably change to a modern <!DOCTYPE html> alone.)
* some output in our custom theme _does_ include XML-style self-closing tags ("<link .... />") which makes the HTML 4.01 transitional parser whinge. If we've switching to non-XHTML (HTML 4.01 transitional or HTML 5) then we should remove the slashes when fixing up the custom theme in future. (Do not *add* slashes per earlier comments in this bug.)
* one element has double 'class' attributes -- the second one should be removed.
Comment 8 Priyanka Dhanda 2011-06-21 18:18:05 UTC
Bugmeister is the new Bugzilla maintainer and default assignee.
Comment 9 Thehelpfulone 2012-06-22 19:18:48 UTC
Resetting to default per bug 37789
Comment 10 Antoine "hashar" Musso (WMF) 2012-06-23 14:31:52 UTC
I have opened a bug request upstream and even submitted a lame patch:

https://bugzilla.mozilla.org/show_bug.cgi?id=767707

Assigning bug to self. I have lowered both severity and priority to the minimal. That is really not killing us and is definitely an easy upstream change.
Comment 11 Antoine "hashar" Musso (WMF) 2012-06-24 13:18:05 UTC
Upstream bug is indeed : https://bugzilla.mozilla.org/show_bug.cgi?id=546838

Aka  Upgrade Bugzilla to HTML5
Comment 12 Antoine "hashar" Musso (WMF) 2012-06-24 13:20:05 UTC
The bugzilla team is not going to update the doctype till some HTML5 is used. I would personally mark our bug as invalid / wont fix, but I am just going to step out of it (removing self of assignee, and un cc). Let this bug rot for a few more years :-)
Comment 13 Antoine "hashar" Musso (WMF) 2012-08-28 09:40:57 UTC
That will be eventually fixed by Bugzilla team one day. Meanwhile, this does not cause any harm to use Bugzilla some I am closing this bug.
Comment 14 Antoine "hashar" Musso (WMF) 2012-11-15 20:17:57 UTC
Just wont fix that bug. Not worth keeping it around I guess. (un ccing myself).
Comment 15 Anu 2012-11-27 11:12:38 UTC
I am not sure if this bug is worth following. I tried to validate some of the best known websites on the link, it gives me errors on google.com websites. Can this bug be closed with that?
Comment 16 Andre Klapper 2012-11-27 12:46:40 UTC
(In reply to comment #15)
> I tried to validate some of the best known websites on the link, 
> it gives me errors on google.com websites.

Not exactly sure what that means. This bug report is about the Wikimedia Bugzilla website not validating against the W3C validator.

While we currently do not plan to fix this in Wikimedia Bugzilla, I'm not against fixing either (so I will not close this as RESOLVED WONTFIX). 
However, any contributions should go into fixing the upstream report at https://bugzilla.mozilla.org/show_bug.cgi?id=546838 first. After that is fixed we can validate which issues are downstream code issues in WM Bugzilla.
Comment 17 Antoine "hashar" Musso (WMF) 2014-01-08 19:47:24 UTC
Ticket solved upstream: https://bugzilla.mozilla.org/show_bug.cgi?id=546838#c10

A commit is updating the HTML templates to change the DOCTYPE from HTML 4.01 Transitional to HTML :D

http://bzr.mozilla.org/bugzilla/trunk/revision/8856

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


Navigation
Links