Last modified: 2006-12-26 05:45:20 UTC
Nasty looking funny? question marks have started to appear? next to redlinks.
This disrupts the flow of? text because you don't? want random question? marks
throughout a sentence. What was wrong? with the old way?? Isn't there
something ''bro?ken'' that needs fixing?
From your bug report (full of qurstion marks), it looks like something screwey
with your computer or browser, not the websites.
1. Check you haven't enabled the alternate broken link display in your preferences
2. Hard-refresh your browser and/or clear your cache
3. If the problem persists, please reopen this bug report and send a screenshot
No, it came on momentarily and then went off again. I think it was someone
messing with the settings for some unfathomable reason. The questoin marks in
the report were supposed to be illustrative.
Sounds like some corrupt CSS was loaded, which is frequent enough to be
irritating, but isn't a problem we can fix per se.
They're back. Redlinks have turned black, lost their underlining and have
acquired question marks at the end of them.
(In reply to comment #5)
> They're back. Redlinks have turned black, lost their underlining and have
> acquired question marks at the end of them.
You checked the user preference again?
Please provide your username and the URL to the wiki on which
you see this effect.
My username is Duncharris. I'm running default Monobook on Firefox (I'll try
upgrading Firefox and see if it has an effect).
No-one's given me a monobook.js present (if that's possible).
I've resaved my preferences and it's working okay now. Something straneg was
happening becaus I didn't touch my prefs.
Generated JS is sending incorrect cache control headers,
which could cause people to sometimes see the wrong style
Cache-Control: s-maxage=2678400, max-age=2678400
It should probably look more like:
Cache-Control: s-maxage=0, max-age=2678400
Vary: Accept-Encoding, Cookie
Brion fixed this some time ago, and the fix seems to have worked; we haven't had
reports of the behaviour since.
*** Bug 2127 has been marked as a duplicate of this bug. ***