Last modified: 2004-11-24 00:30:57 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 815 - closed bugs not being styled (e.g. with strikeout)
closed bugs not being styled (e.g. with strikeout)
Product: Wikimedia
Classification: Unclassified
Bugzilla (Other open bugs)
PC Windows 2000
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2004-11-01 17:07 UTC by Rowan Collins [IMSoP]
Modified: 2004-11-24 00:30 UTC (History)
2 users (show)

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


Description Rowan Collins [IMSoP] 2004-11-01 17:07:20 UTC
One of the features that's quite nice with bugzilla is that anywhere a link
occurs to a closed bug, it is styled differently (crossed out) to make this
clear. This even, I believe, applies to the links created by just typing "bug
804" or whatever in a comment.

However, the "MediaZilla" stylesheets seem to be lacking this styling. I think
it just needs someone to add a CSS rule for the "bz_closed" style, as the links
are being enclosed in <span style="bz_closed">...</span>. It would be very nice
to have this feature working, as it makes things like lists of dependencies much
more useful.
Comment 1 Rowan Collins [IMSoP] 2004-11-23 20:37:58 UTC
Note that strikeout should also be applied to the class bz_obsolete, which is
used for patches which have been marked as obsolete. 

Oddly, the source for this page seems to link to and but neither seems to actually
exist/be accessible. Maybe the rules are in there, but the files are in the
wrong place or have bad permissions or somesuch malarkey.
Comment 2 Brion Vibber 2004-11-24 00:30:57 UTC
Yeah, there was a permissions problem; when I upgraded us from 2.18rc2 
to 2.18rc3 a lot of files in the CSS subdirectory got reset to be unreadable. 
Should be fixed now.

There is in fact no edit_bug.css in 2.18rc3; not sure what's up with that.

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