Last modified: 2011-01-25 01:21:00 UTC
It will be really handy if when the skin switch occurs, people who have a monobook.js are guided on how to get their scripts working on vector (mostly, USING vector.js instead). I see this as one of the primary problems for experienced editors.
Now that we have a common.js for users, shouldn't scripts be made to work in any skin and put there instead? That being said, I think a note on preference saves saying something about checking your CSS/JS might work ok.
(In reply to comment #1) > Now that we have a common.js for users, shouldn't scripts be made to work in > any skin and put there instead? > Do we? Is this code live on Wikipedia yet? > That being said, I think a note on preference saves saying something about > checking your CSS/JS might work ok. I don't know the exact plans but I'm pretty sure we'll announce this migration through site notices and the like; we could add a phrase about migrating one's user JS.
no, user/common.js is not deployed yet. Unfortunately :( @Roan, I figured we could find a way to see if people have a monobook.js, and then direct them to a help page. Though I guess such a detection would create a serious caching problem. Well then perhaps a normal link to a help page might be an idea. I think i wrote something down before, can see if I can turn it into a page.
This is too late now. No longer useful.
Just because it didn't happen with en.wp doesn't mean this shouldn't happen if & when Vector is roll out across other languages and or projects. More generally, this should probably exist anyway for anyone who changes their skin in the preference.
*** Bug 23887 has been marked as a duplicate of this bug. ***
Added a reference on Special:PrefSwitch in r68379
