Last modified: 2013-10-05 08:40:51 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 T53766, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 51766 - ResourceLoader didn't invalidate cached CSS correctly for #toc change
ResourceLoader didn't invalidate cached CSS correctly for #toc change
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
ResourceLoader (Other open bugs)
unspecified
All All
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on: 51394 51685 51763
Blocks: 54945
  Show dependency treegraph
 
Reported: 2013-07-21 05:11 UTC by Liangent
Modified: 2013-10-05 08:40 UTC (History)
8 users (show)

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


Attachments

Description Liangent 2013-07-21 05:11:39 UTC
See bug 51685. Bug reports kept coming in village pump.
Comment 1 Andre Klapper 2013-07-22 12:07:27 UTC
(In reply to comment #0)
> Bug reports kept coming in village pump.

Any links?
Comment 3 Bartosz Dziewoński 2013-07-22 12:15:13 UTC
Change which caused this: I4ecd0659d1f955a9b593d281a3fef0a81c218a52 to fix bug 658.
Comment 5 db [inactive,noenotif] 2013-07-30 19:13:31 UTC
Looks like a IE8 problem.
Comment 6 Liangent 2013-08-06 13:55:33 UTC
(In reply to comment #5)
> Looks like a IE8 problem.

I saw it in Firefox myself.
Comment 7 Bawolff (Brian Wolff) 2013-08-20 22:41:59 UTC
I'm having a similar problem with gallery tag changes that got deployed yesterday. Some people are reporting not seeing the new css on commons. Telling them to do a hard refresh fixes, but this sort of thing shouldn't happen.
Comment 8 Krinkle 2013-10-04 14:51:42 UTC
Closing this bug because this particular issue (#toc change) has long since expired from the caches and is no longer relevant. We tried to fix it at the time, and I think we eventually got it to purge. If not, it has resolved itself through time as every cache I can think of has expired by now.

We'll probably never know which cache was guilty.

Please file a new bug for something that may or may not sound similar (feel free to link it to bug 54945 if it seems ResourceLoade related).

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


Navigation
Links