I am a little weary changing this behavior inside the toolbar itself.
Sun, Jun 16
Thu, Jun 13
Yup, that would work as well; I wasn't sure if it was okay to change that without some agreement from community if the bot is widespread, which is why I (wrongly) assumed that wasn't an option :)
I was thinking about this -- I don't think OAuth is enough to stop this behavior. We will need to add a check about whether the user is also blocked, potentially from the page they're asking the bot to edit.
Tue, Jun 11
Wed, Jun 5
Tue, Jun 4
Fri, May 31
Yes, I don't think that's a problem, that's the intent.
Thu, May 30
Tue, May 28
There's not a lot of specifics to test here, but we should just verify that things didn't break with this on beta.
This is an interesting discussion, but it's not quite for this product to make the decision. We read the spec off of TemplateData which allow template owners (and wikis) to set the templates the way they wish they behave for better behavior both on the wiki as well as while being edited by this tool or VisualEditor.
Actually, that's a great catch; this should probably also be the fallback for wikis where Echo isn't installed.
Yeah, this fix is mostly only for the UX of the tool and should not impact the actual SVG file.
Fri, May 24
PR available: https://github.com/wikimedia/svgtranslate/pull/114
Eh, yes, good point about the API. We can find a solution for that, but to be fair, that might well be acceptable behavior. The API module is split between local and global preferences, since the users of the API don't have core's problem of not having to know about the existence of GlobalPreferences. The explicit product choice (until now at least) was that whoever wants to change the preferences through the API needs to explicitly choose either local API or global.
GlobalPreferences is listening to the UserSaveOptions hook, which hands over the $options array that can then be handled. See https://github.com/wikimedia/mediawiki-extensions-GlobalPreferences/blob/master/includes/Hooks.php#L91
Thu, May 23
One question is also where this wg variable "lives"; GlobalPreferences shouldn't really have a list of options in it, so we can put this in Config, but we will have to make sure that all given options are global (not per wiki). Could use your input on this, @MaxSem
May 18 2019
May 14 2019
I'm using Chrome Version 70.0.3538.77 (Official Build) (64-bit)
May 7 2019
May 6 2019
The 'prevents' method is dealt with and had an email sent to wikitech-l.
May 5 2019
The problem with flashing will be Varnish; logged-out users "skip" our PHP servers because they're served from cache. That's why most pages will "flash" to them.
To clarify -- the lazy-loading is for whatever JS interface we come up with to toggle, not to initial style loading (it was especially important when we discussed a popup, which involves OOUI assets and is hence not that small)
May 3 2019
One more thing, sorry for the flood here, but we might need to lazy-load the CSS styles. If we do, there might be a few milliseconds (potentially a little more to slow connections) between the user clicking the toggle and the CSS/JS being loaded and activated.
Ooh, those look really nice, I think they work better than a popup (and as mentioned, we will have a much easier time making them accessible; the menus tend to be problematic with that)
@MusikAnimal Are we using this ticket to add the initial files (+ linting + folder structure + tests / grunt, etc) for the extension or do you want to use the other ticket to do that?
May 2 2019
Apr 30 2019
For the extension files, you can use MWStew: https://tools.wmflabs.org/mwstew/
Apr 12 2019
Merged. Should be in staging in a few minutes.
Apr 11 2019
Apr 9 2019
When did we introduce this? If we introduced it in a previous (and published) release, we might need to deprecate for the upcoming one? ... But if it's in between releases it's probably fine.
Apr 3 2019
Apr 2 2019
This is the quite entangled view of the "Enhanced" recent changes table. The structure is tabular, but this specific cell has several notations in it (like "N" for new page, etc) and in order to align them across the different entries, the line is either with the symbol, or with a space.
Apr 1 2019
Mar 31 2019
Mar 30 2019
Mar 29 2019
Just note that browsers started considering these custom messages as security breach. They allow us to display a warning before navigating away, but not to set the text of that warning.