On 03/05/2013 10:50 PM, Krinkle wrote:
> Considering the "global" aspect it may be more useful (and flexible) to
> enforce this from the global script instead of from local preferences, which
> are rather annoying to maintain imho.
>
> if ( dbname == wikidatawiki || .. ) {
> return;
Good point
On Mar 6, 2013, at 2:43 AM, Matthew Flaschen wrote:
> On 03/05/2013 09:27 AM, James Forrester wrote:
>> You can of course always counter-over-ride your global JS/CSS locally - the
>> composite rule would presumably be changed to:
>>
>> 1. file,
>> 2. site
>> 3. skin,
>> *. global-user
>> 4. loca
On 03/05/2013 09:27 AM, James Forrester wrote:
> You can of course always counter-over-ride your global JS/CSS locally - the
> composite rule would presumably be changed to:
>
> 1. file,
> 2. site
> 3. skin,
> *. global-user
> 4. local-user
However, it's trickier to override JS then override CSS.
Not rubbish - that would be quite useful. The only problem is it would
be a somewhat limited use case. Many users never go near their css/js,
so it would just be another checkbox for them to ignore, and those who
do use global css/js would just as likely have wider scope issues than
that - only
You can of course always counter-over-ride your global JS/CSS locally - the
composite rule would presumably be changed to:
1. file,
2. site
3. skin,
*. global-user
4. local-user
… - so you could fix local incompatibilities.
J.
On 5 March 2013 09:14, Isarra Yos wrote:
> Not rubbish - that wo
Not rubbish - that would be quite useful. The only problem is it would
be a somewhat limited use case. Many users never go near their css/js,
so it would just be another checkbox for them to ignore, and those who
do use global css/js would just as likely have wider scope issues than
that - only
I may be saying rubbish, but...
I think we should have a checkbox in Preferences where we can switch off
global JS and CSS for the wiki where this checkbox is set/unset. Let's
imagine I have a script which fits well for every project but Wikidata.
Then I go to the preferences and just disable the
On 4 March 2013 14:59, Krenair wrote:
> On 04/03/13 22:57, Matthew Flaschen wrote:
>>
>> Has anyone looked at allowing a user to have global CSS and JS across
>> all WMF wikis?
>>
>> I know you can hack it with a mw.loader.load on all the wikis you use,
>> but it would be useful if CentralAuth had
On Mon, Mar 4, 2013 at 2:59 PM, Brian Wolff wrote:
> Somebody (pathoschild maybe) used to have a bot that copied over css files
> from meta. (Why people didnt just dynamically load things I don't know)
https://meta.wikimedia.org/wiki/User:Pathoschild/Scripts/Synchbot
> On 2013-03-04 6:57 PM, "Mat
Somebody (pathoschild maybe) used to have a bot that copied over css files
from meta. (Why people didnt just dynamically load things I don't know)
On 2013-03-04 6:57 PM, "Matthew Flaschen" wrote:
> Has anyone looked at allowing a user to have global CSS and JS across
> all WMF wikis?
>
> I know y
It seems so, yes: https://gerrit.wikimedia.org/r/7274
Bug: https://bugzilla.wikimedia.org/13953
On 04/03/13 22:57, Matthew Flaschen wrote:
Has anyone looked at allowing a user to have global CSS and JS across
all WMF wikis?
I know you can hack it with a mw.loader.load on all the wikis you use,
Has anyone looked at allowing a user to have global CSS and JS across
all WMF wikis?
I know you can hack it with a mw.loader.load on all the wikis you use,
but it would be useful if CentralAuth had it built in.
Is there a bug for this?
Matt Flaschen
_
12 matches
Mail list logo
