Hi, Roan. I think a slightly longer version is a good idea 🙂.

We don't have a separate tutorial or a page about updating articles. Are these blockers?

The Homepage suggests to users to read a page that explains what Wikipedia is and how it works. Any page is fine, as far as it is not cal for action (like https://pl.wikipedia.org/wiki/Pomoc:Pierwsze_kroki does).

Tutorial (Q915263) -- this seems wrong. It links to a historical tutorial.

Manual of style (Q4994848): https://pl.wikipedia.org/wiki/Pomoc:Styl_%E2%80%93_poradnik_dla_autor%C3%B3w. More or less... We don't have such a large compendium as enwiki, but should be enough for beginners.

This is all done:

• Translate the interface (on translatewiki.net, needs a specific account)
• Translate the documentation
• https://www.mediawiki.org/wiki/Growth/Focus on help desk/Help panel (resource for newcomers)
• https://www.mediawiki.org/wiki/Help:Growth/Tools and subpages (resource for mentors and newcomers)
• https://www.mediawiki.org/wiki/Growth/Communities/How to work with newcomers on help desks (resource for mentors)
• https://www.mediawiki.org/wiki/Growth/Communities/How to introduce yourself as a mentor (resource for mentors)

The search bar looks better in this version, but the sidebar toggle looks awkward in this version. The toggle don't seem to be connected with the sidebar in any way. And also the icon ("<<") don't seem like something that you can naturally recognise as a menu thingy.

Just a note -- same happens on pl.wiki on Vector2/Timeless. Firefox 78.

Sorry. Almost immediately after posting I noticed that the problem is opened paragraph. And also inline template must be surrounded with a paragraph.

Interface translation is done. Probably needs testing, but I finished all yesterday/today 🙂. Edit: just as a note - I just run the final mile. Did not want to suggest I did it all by myself 😊

User forks a script or gadget in own user space

Hi. There are still some false positives.

Note: This task is about an issue that exists only in development (and maybe testing) environments but it doesn’t affect production websites. The issue is that when translating an article, user-defined categories are not saved properly, they are totally ignored.

Nevermind. Seem to be a caching issue.

That don't seem to be affected
https://pl.wikipedia.org/wiki/MediaWiki:Gadget-Blackskin.css

Yes, your assumption is correct -- I changed the refs in the translation tool.

Sorry, I thought that was universal. I guess "Advanced mode" setting is crucial here.

Not sure if its a duplicate. On my side the problem is different (I cannot load the translation, not save it).

In T238038#5727398, @TheDJ wrote:

Question. https://wikitech.wikimedia.org/wiki/HTTPS/Browser_Recommendations

Windows 7: I know it CAN support TLS 1.2, but I can't figure out if Microsoft released a patch to enable it by default.. This influences if IE11 is still a supported browser on Windows 7 (effectively, as we can't ask people to modify their registry).

I'm happy to say problems you describe don't exist 🙂. After a day of finding weird security bugs (in other companies) I'm happy to report this works as expected 😎.

I understand that position on adding properties, but normally when something is not standardized its kind of experimental. When it's experimental and can change the name can still be different etc... But that is different here. The property worked everywhere from ages. It will not change. It is already implemented. So there are simply no risks of change.

To my knowledge using SVG in background image is safe. At least in that script will not be executed in that context. So the browsers actually does the check for you. You can do weird things (like fa* tags for graphic filters), things that can be heavy for users, but not strictly unsafe. At least not to my knowledge.

If we allow forking these to user css/json/js pages, when merging back there could be edit conflicts considering another edit could have been merged and the user didn't pull. How would you suggest keeping a fork to user namespace be kept up to date, might need to keep track of diff changes - this gets complicated?

I think what is needed is forking, not branching.

Hi. I just fixed my tool on toolforge, but... Am I correct to assume that actor_user is null only for anonymous actors (IP)?

BTW. Might be a good idea to also add a link to skip the diff and go directly to the contents of the article (if someone doesn't have time to review changes).

Screen from some random article that awaits flagging
https://pl.m.wikipedia.org/wiki/Lion_Vibrations

Original author of this request explicitly stated that "Wikimedia software does not allow external links; presumably for spam reasons; however, if the link is internal, it should be allowed (just as wikilinks are allowed)".

I see this differently. Note that I'm using regexp. So when I match "(.+)" I get a selection on a link with quotes around it so parentheses should match HTML/wikicode that contains the link. In other words - $1 should contain markup equivalent of [[blah]]. If that would be possible to do you would get following cases:

Edited to correct two things:

I'm saying this happens very often on many pages. It's just not happening every time.

This is caused by the fact that Resource Loader broken compatibility with old scripts (mostly because making order of custom scripts completely unpredictable). This is supposed to be fixed with Gadgets 2.0 also allowing creation of custom (user) gadgets. I'm not sure when is this coming and if it will deliver...

OK, that seems to work now (also for new graphs), so probably temporary as you said.

Does this supposed to work?
https://pl.wikipedia.org/wiki/Wikipedysta:Nux/nuxTBKeys.js