Last modified: 2013-09-04 11:49:36 UTC
I already mentioned this bug at https://bugzilla.wikimedia.org/show_bug.cgi?id=29585 but I think it deserves a separate bug report. > I unchecked "Format broken links like this (alternative: like this?)" in user's > preferences and have clicked "Save" button. After this (and pressing F5) > formatting of links haven't changed for this user. > > I will create a new user and try to configure it anew, as a bug workaround. Maybe it is caused by me used "Rename user" module?
ugh, I hoped that preference had died :P ---- What browser btw. that preference isn't supported on all browsers (For example on lynx, older IE) ---- As an aside, parser cache does not vary based on that preference, so it has nothing to do with bug 29585.
Hmm, the user.options module does appear to be broken on MW 1.17 (only the js is loaded. CSS is not) but it seems fixed in 1.18...
(In reply to comment #1) > ugh, I hoped that preference had died :P > > ---- > > What browser btw. that preference isn't supported on all browsers (For example > on lynx, older IE) Firefox 8.0 for Linux. > As an aside, parser cache does not vary based on that preference, so it has > nothing to do with bug 29585.
(In reply to comment #2) > Hmm, the user.options module does appear to be broken on MW 1.17 (only the js > is loaded. CSS is not) Showing or not showing question signs after a word is not related with CSS. > but it seems fixed in 1.18... I will probably update.
I created a new user. The preference does not work with this new user also. :-(
(In reply to comment #4) > (In reply to comment #2) > > Hmm, the user.options module does appear to be broken on MW 1.17 (only the js > > is loaded. CSS is not) > > Showing or not showing question signs after a word is not related with CSS. The "?" is in fact added via CSS: $rules[] = "a.new, #quickbar a.new, a.stub, #quickbar a.stub { color: inherit; }"; $rules[] = "a.new:after, #quickbar a.new:after { content: '?'; color: #ba0000; }"; $rules[] = "a.stub:after, #quickbar a.stub:after { content: '!'; color: #772233; }"; so missing CSS would cause that.
I can confirm this is fixed in 1.18. Thanks for the report.
