Last modified: 2014-08-29 11:46:36 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 T50753, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 48753 - MonoBook: Remove text-transform from personal toolbar links
MonoBook: Remove text-transform from personal toolbar links
Status: NEW
Product: MediaWiki skins
Classification: Unclassified
MonoBook (Other open bugs)
unspecified
All All
: Lowest enhancement
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-23 18:04 UTC by Ryan Kaldari
Modified: 2014-08-29 11:46 UTC (History)
2 users (show)

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


Attachments

Description Ryan Kaldari 2013-05-23 18:04:52 UTC
There's no reason the personal toolbar link should be lowercase in monobook, especially since they are all on one text line (and thus appear to run together as a sentence) and it doesn't make sense for certain languages (where the capitalization is important for meaning). The sidebar navigation links are in regular sentence case, so these should be the same for consistency.

This also avoids the problem of elements inheriting the text-transform, such as the notifications flyout (although there is a workaround in place for it currently).
Comment 1 Ryan Kaldari 2013-05-24 01:22:50 UTC
The patch for this (which was abandoned in favor of this bug) is change Id8dd1454.
Comment 2 Bartosz Dziewoński 2014-08-29 11:46:36 UTC
Quoting myself from the patch:

They have always been this way. This is an integral part of the skin.

The solution to not having text-transform applied to non-portlet items inserted inside the portlet is not to insert non-portlet items inside the portlet.

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


Navigation
Links