Fri, Sep 25
Please contact Jazmin or Olga to set expectations and ensure this work gets scheduled. This extension is currently going through a code stewardship review so is unlikely to get worked on by us otherwise.
Please contact Jazmin or Olga to set expectations and ensure this work gets scheduled. This extension is currently going through a code stewardship review so is unlikely to get worked on otherwise.
The more menu has always worked like this as far as I'm aware and Im not sure what the problem statement is here. Most users do not see this.
I don't have deploy rights, but I can be around to test if necessary. Peter should be finished for the day.
The raw HTML contains an onclick handler and has a collapsible-section class on all sections. Without those there will be a reflow as the section collapsing is applied. The onclick handler accounts for slow connections and connections where JS doesn't fully load. I can confirm our refactors removed those (accidentally) and that the above patch fixes this.
Thu, Sep 24
this would be helpful in the new ContentTranslation skin: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ContentTranslation/+/627982
Clear tail off with group1 wikis after Wednesday deploy.
This came up on hacker news today
Earlier today we had 50k errors in 12hrs about 50% of coming that from gadgets which I've had to since fix to get these numbers down. T263688 is another example of something that's becoming a challenge as we roll out further.
Wed, Sep 23
Thanks for working on this! We will need patches for Vector and Monobook removing this code to avoid duplicating the menu item.
I think it's fine to ship this to Modern.
I think we can just disable this test for now. Was hoping it was just a blip. Is there a way to disable a test so it is only disabled on CI?
Tue, Sep 22
Thanks for this information @TJones - it's really useful.
Waiting for Olga but I assume I'll be working on this one
I think this is fine. Likely an existing problem.
This still seems to be occuring and my understanding is that T261522 is in production now?
At 107 errors a day this is one of the more common errors in our production code.
Mon, Sep 21
The EditAttemptSchema hardcodes phone for the mobile editor - https://gerrit.wikimedia.org/g/mediawiki/extensions/MobileFrontend/+/774c791467ab457c1d41c7328f0240d7e22aa2e6/src/mobile.init/eventLogging/schemaEditAttemptStep.js#38 - until recently that was logging desktop Minerva edit's as 'phone'. I'm not sure how VisualEditor does it, but I imagine it also relies on mobile/desktop domain to determine platform value.
^ see above comment
Someone is using a phone or tablet to edit with the Wikitext editor on the desktop site (which I do commonly)
Sorry my screenshot was confusing. Let me try that again.
Not being actively worked on anymore, however see T262936 for progress with push notifications.
That works for me. I'm happy to jump on any editorial/copy-edit fixes this week so let me know!
It's not possible to remove JS modules in extensions. Extensions can only add. Minerva's hook does allow modification but I think that's an anti-pattern as it creates unnecessary fragmentation in the code that runs on Minerva.
This should be fixed now on the beta cluster. The variants https://zh.wikipedia.beta.wmflabs.org/zh-hk/Main_Page and https://zh.wikipedia.beta.wmflabs.org/zh-sg/Main_Page for example show different logos.
These are all pretty easy, as they decorate the existing logo rather than replace it entirely.
The most interesting one is this one, which does seem to substitute the globe and this can be achieved by using a pseudo element that overlaps the existing logo:
Presumably this needs to be done in SkinMustache::buildSearchProps in core, yes as part of the making of html-input
Is there some guidance we can give the gadget developers? I hadn't noticed the WeaselWords script being involved here. I'm also happy to push a fix to the wiki page if it's a relatively easy one.
All errors go through the global.error event. if Vue is swallowing these errors
- Rollback will require ops
- It's not just search in header - it's also DOM changes
- We're a little concerned 2 weeks won't be enough data.
Sun, Sep 20
Sat, Sep 19
There were 37 errors in last 12hrs from 4 IPs While 4 of those came from Firefox 67 and 52, 33 came from 2 IPs using Firefox 79 a much more modern browser . That said the errors are still low (for now) but I think it's wrong to dismiss this just on age.
Fri, Sep 18
This bug was pretty easy to replicate and fix using debugger and breaking and the fix seemed pretty obvious to me.