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?
Version: 1.19
Severity: normal
Attached:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T33217 MediaWiki bugs to be fixed for 1.19wmf1 deployment (tracking) | |||
| Declined | None | T36504 [Regression] There should not be a mismatch between html and stylesheet version |
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.
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?
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...
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?