Last modified: 2012-11-01 22:54:47 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 T31718, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 29718 - Underline option only works for legacy skins
Underline option only works for legacy skins
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
User preferences (Other open bugs)
1.20.x
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-07-05 16:23 UTC by Robin Pepermans (SPQRobin)
Modified: 2012-11-01 22:54 UTC (History)
6 users (show)

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


Attachments

Description Robin Pepermans (SPQRobin) 2011-07-05 16:23:00 UTC
By default:
* Links are underlined only on hover for vector, monobook, etc
* Links are always underlined for legacy skins like cologneblue, standard

The underline option of Special:Preferences only works for the legacy skins (default is browser standard which is afaik nearly always "underlined").

Solutions:
* If this is the intended behaviour, it should be mentioned on Special:Preferences that it only works for those skins
* The option can be extended to work on all skins
* The option can be removed as it is trivial and can be done by simple CSS

(In general, more clean-up is needed for preferences & skins.)
Comment 1 Chad H. 2011-07-07 16:19:25 UTC
(In reply to comment #0)
> * The option can be removed as it is trivial and can be done by simple CSS
> 

+1. Such an option would never have made it in these days, we would've told the person suggesting it to use site or user CSS to get such an effect.
Comment 2 Derk-Jan Hartman 2011-07-07 17:31:43 UTC
I'm quite sure this works on trunk. Perhaps we forgot to backport a fix ?
Comment 3 Robin Pepermans (SPQRobin) 2011-07-07 17:52:41 UTC
The thing is that the default option "browser default" behaves differently per skin: legacy skins really use the browser default (always underline), while vector etc have CSS that override this: a { text-decoration: none; } a:hover { text-decoration: underline; }

The other two options (never or always) do work correctly for all skins, afaik.

Still, it may be a good idea to just remove this option. It was likely introduced for RTL languages which is no longer needed (see bug 29712).
Comment 4 Derk-Jan Hartman 2011-07-07 20:00:40 UTC
I don't see the problem ... 
Why don't we just rename the option "browser default" to "skin default"...
Comment 5 Bartosz Dziewoński 2012-10-10 16:42:04 UTC
This option is being removed with https://gerrit.wikimedia.org/r/#/c/27201/.
Comment 6 Sumana Harihareswara 2012-11-01 16:41:09 UTC
Gerrit change was abandoned - see discussion there as to why.
Comment 7 Bartosz Dziewoński 2012-11-01 16:46:14 UTC
Not reproducible (anymore). Closing as WFM.
Comment 8 Robin Pepermans (SPQRobin) 2012-11-01 22:20:22 UTC
Hmm? Not reproducible? Afaik nothing changed since I submitted the bug, but I see you submitted https://gerrit.wikimedia.org/r/#/c/31268/ - which is good, I should've done it earlier.

Reopening until that change is merged.
Comment 9 Robin Pepermans (SPQRobin) 2012-11-01 22:30:31 UTC
Merged the change myself now :)
Comment 10 Bartosz Dziewoński 2012-11-01 22:40:56 UTC
Sorry, I interpreted "only works for legacy skins" as "changing the setting doesn't actually work in other skins".
Comment 11 Robin Pepermans (SPQRobin) 2012-11-01 22:54:47 UTC
(In reply to comment #10)
> Sorry, I interpreted "only works for legacy skins" as "changing the setting
> doesn't actually work in other skins".

Just to clear things up... My initial bug report was based on what the description says: browser default => always underline => I saw it wasn't underlined in vector etc => I concluded it didn't work there... But now we changed the description to say what it actually does (browser AND SKIN dependent), so all is fine :)

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


Navigation
Links