[12:35:16] Volker_E: [12:35:56] would you say for an expandable interface it's better to use an indicator to make the state visible [12:36:01] or an icon? [12:36:19] in the RevisionSlider we use the icon with collapse and expand [12:36:43] the AdvancedSearch uses the indicator that only allows up and down [13:33:33] CFisch_remote: so far we have no clear answer [13:33:47] CFisch_remote: from style guide perspective [13:34:30] ok :-) [13:35:14] CFisch_remote: I think with RevisionSlider it makes sense to use the icon as the triggering handle can be so long, that a stronger (as in easier to recognize), and therein bigger icon makes sense [13:36:09] AdvancedSearch from the task I've seen is clearly an indicator as it's a more a normal form field [13:36:43] CFisch_remote: We need to fill this into a guiding principle at some point :) [13:38:23] yeah depends I would say - we have two indicators there now: One is for expanding the advanced search form fields .... this is more in the direction of what's happening with the RevisionSlider ... the other thing is the MenuTagMultiselectWidget for the namespace selection that is basically an input field that expands to select items [13:39:28] but for a consistent look it might not make sense to use the expand/collaps icons for the one thing and the up/down indicators for the other ^^ [13:39:50] so I guess we will just stick to the indicators for now ... was just wondering [13:39:54] thanks so far :-) [17:49:30] hi I have a question. Is there any way I can disable the New Filters for Recent Changes globally? I would prefer to use one unified interface across all WMF projects [17:52:28] Basically, no [17:52:31] We don't have global preferences [17:52:54] Reedy: could api set them? [17:53:10] If you write something to iterate over every wiki, I guess so [17:53:17] Hmm [17:53:40] it wouldn't be difficult [17:53:40] not something like we had for mediaviewer? [17:53:48] I couldnt do that (my js is a little rusty) but if someone could be found im sure that would work [17:53:53] with a mw.config.set? [17:54:10] so i can just put it on my global js to disable it that way [17:54:45] you can write a global script that updates your preferences as soon as you visit the wiki [17:54:46] I know that would be a hacky method to do it, but its all we have [17:54:51] but it's a terrible hack [17:54:57] yea I know [17:55:03] tgr: worse has been done before [17:56:11] mhm, I guess theres no other option than to manually disable it per wiki [17:56:36] I'm no script writer so that one is out of the question [17:56:40] the nice thing to do would be to fix https://tools.wmflabs.org/globalprefs/ to handle other preferences than language [17:57:58] mhm nice tool [17:58:11] its kinda something I actually needed too :P [17:58:48] other than that, either write a script to iterate through all your wikis and set the pref via API (using bot passwords or maybe centralauthtoken so you don't need to log in everywhere) [17:59:22] or write a m:MediaWiki:Global.js script that checks the preference and updates it if it is not the correct value [17:59:34] the latter is probably easier but also more hacky [18:00:15] yea, I'm no real script writer to be honest so both of those are not going to work sadly [18:00:20] so I'm out of luck [18:00:31] atleast thanks for thinking about :) [18:00:43] I would write one but it wouldnt work xD [18:03:05] mw.loader.using( 'mediawiki.api.options', function() { var api = new mw.Api(); if ( mw.user.options.get( 'wprcenhancedfilters' ) { api.saveOptions( 'wprcenhancedfilters', 0 ); } } ); [18:03:10] something like that [18:03:35] does that disable it when visiting a wiki that has it? [18:04:03] yeah, but I haven't tested so I'm sure it needs some debugging [18:04:41] let me test it [18:04:48] I would probably make it log to browser console to ensure it properly works but thats just my opinion [18:07:10] I don't think its working after trying to test it on fawiki (which uses FlaggedRev, where its the default)