Last modified: 2012-05-03 02:42:45 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
First Last Prev Next    This bug is not in your last search results.
Bug 34504 - [Regression] There should not be a mismatch between html and stylesheet version
[Regression] There should not be a mismatch between html and stylesheet version
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.19
All All
: Normal normal (vote)
: 1.19.0 release
Assigned To: Nobody - You can work on this!
: code-update-regression
Depends on:
Blocks: 31217
  Show dependency tree / graph
 
Reported: 2012-02-18 23:41 UTC by Krinkle
Modified: 2012-05-03 02:42 UTC (History)
3 users (show)

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

Attachments
Example (188.00 KB, image/png)
2012-02-18 23:41 UTC, Krinkle 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Krinkle 2012-02-18 23:41:25 UTC 
Created attachment 10042 [details]
Example

Could be wontfixed if there's a sufficient work-around.

This is what was causing the "Jump to navigation" links to appear on cached pages after the 1.19 roll-out. Also when 1.17/Vector was introduced, this bug broke a gazillion pages by turning their layout into an ugly mess for ~ 30 days due to cache html and stylesheet references.

Fixable?
Comment 1 Brion Vibber 2012-02-21 18:59:27 UTC 
The 'fix' I think would be to do some time-traveling so that we ensure that old stuff gets delivered with old HTML. But I'm not sure how possible that is; if old styles are out of cache then we'll end up with the new styles/scripts even if we "ask" for the old one in the timestamp on the request.

Traditionally, we intend for new CSS to apply validly to old HTML to work around this problem. If new CSS doesn't fix old HTML, then you get problems until the old HTML vanishes from cache.
Comment 2 Brion Vibber 2012-02-21 19:03:35 UTC 
Is this bug tracking the 'jump to' link issue specifically (eg, fix the styles so they're hidden again!) or is that already resolved and this is a general issue/idea/question?
Comment 3 Roan Kattouw 2012-02-21 19:05:03 UTC 
Probably the best thing to do would be to add CSS rules for back compat.
Comment 4 Brion Vibber 2012-02-21 19:17:47 UTC 
r98045 looks like a culprit
Comment 5 Brion Vibber 2012-02-21 19:20:26 UTC 
It looks like switching .mw-jump to #jump-to-nav in shared.css will resolve this. Not sure why a new class was added here and the styles split...
Comment 6 Brion Vibber 2012-02-21 19:25:47 UTC 
r112034 fixes the style so it should work with old pages, please merge/deploy.
Comment 7 Rob Lanphier 2012-02-24 15:57:45 UTC 
Since the original symptom behind this bug report is fixed, we need to decide how we're going to dispose of the original suggestion.  Should we "wontfix" or leave open?
Comment 8 Mark A. Hershberger 2012-02-24 21:54:48 UTC 
wontfix per triage
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links