Sat, Sep 26
@kst This is unlikely to be fixed as the minimum width was added intentionally. Add the following CSS to your global.css to undo it:
Thu, Sep 10
@hashar That's really thorough research. Calling array_unshift (prepend in English) one-by-one on the features list reverses the order of those as "normalize" is prepended, then "elementes", etc.
What it should do is to accumulate the ResourceLoaderFilePaths in a new array then array_unshift that new array to $styles[$mediaType].
Wed, Sep 9
But you aren't the target audience ;-) Volunteers - like myself - have a more direct view of what can be achieved on each forum.
I see. Yes, the personal experience part about ineffectiveness came through ;-) Anyway I would suggest a bit reducing the size and adding more content.
- Apart from Mattermost we also have Zulip for outreach programs, we have the #wmhack group on Telegram which is used by quite some folks for general questions not Hackathon related, and probably many other places, so I intentionally went for established places which have a larger number of users now.
All these are quite hard to find. I recall spending hours looking for places where I might get answers to my questions. In the end my questions remained unanswered and I haven't found these places either.
From my personal experience: it would help to add all these 3 you've listed (I'm not against adding the rest 😄). People will choose the one that's closest to their area of interest and/or the most familiar/accessible of these tools.
I think a proactive approach would be beneficial here: the only way to transition from outdated, but very well established solutions toward modern, more effective and convenient ones is to promote those, thus being less established is extra reason to advertise them, otherwise the fate of discourse might repeat itself.
Tue, Sep 8
As the author of the patches and the task.
@Aklapper Two feedback on the discourse notice:
- The font is huge, I think half the size would be sufficient for readers to notice.
- The recently launched Mattermost chat can serve as an easily accessible alternative (unlike IRC) or even continuation of the discourse instance, therefore I hope you could add that to the notification also:
I'm sorry for the misunderstanding. It would help to clarify what "As a software engineer in Wikimedia Germany" means in that case and how much difference WMF or WMDE makes in regards to affiliation.
Mon, Sep 7
And Ladsgroup declining the task twice.
Aug 25 2020
@Ammarpad The removal of the call to setupSkinUserCss() in https://gerrit.wikimedia.org/r/c/mediawiki/core/+/619144/2/includes/OutputPage.php
broke many skins from the following list as these no longer load their stylesheets:
Thank you, @Huji.
This is caused by the notification (Echo) icons' hidden text (only used by screen readers). The shape that you see is where that short text ("Alerts (0)", "Notices (0)") would be.
The issue is caused by an unfortunate DOM design in the Echo extension, Vector has nothing to do with it.
Aug 24 2020
@Darwinius Thank you, I'm sorry to hear that. This sounds like a very pressing issue.
Aug 23 2020
Aug 21 2020
Aug 20 2020
Aug 19 2020
FYI this can be reproduced in Chrome DevTools' mobile view (emulator) after switching to Classic View.
Jul 22 2020
Jul 21 2020
Jul 8 2020
Jul 7 2020
The DEMO is ready: http://patchdemo.wmflabs.org/wikis/cedef736804997e570ad35c605f6322b/w/
@Jdlrobson There is a fully fleshed-out implementation reviewed by 2 persons that you've promised to review for 2 months. Is there any benefit in working on a competing, half implementation instead of reviewing one that's ready?
@Volker_E the images don't demonstrate the problem nor the solution. I have a guess what the task is about, but the description is unclear, so I might have guessed wrong.
Note: unless T254277 is implemented, the tab collapsing can cope with too many tabs on smaller screens too.
The logo as a link is redundant with the "Main Page" sidebar link. Navigates to the main page when clicked is ok, but IMO it should not be part of the TAB sequence at all. Pressing TAB twice will bring you to: -> sidebar button -> "Main Page". That's sufficient.
Obviously it was a mistake, but I clearly and explicitly asked him to do so. Given that I've been repeatedly instructed to answer his questions - before I got to doing so -, I expect my requests would be responded to as well. That did not happen.
Initial thoughts republished from wikitech-l:
As Nray's patch is almost done, we could revisit a minor detail that was descoped from the previous patch. The sidebar button's focus outline in Firefox is different from the regular focus outline. Fix, using the already established solution: patch 607311
Thanks for the test!
I'd be interested to see such example, I haven't seen any yet.
Just a quick personal note: "Wikitext" sounds more descriptive and familiar in this context. Even as a developer I'd prefer it to "Source".
It's great this question is asked.
Splitting would be helpful, I agree.
There is a 3rd part that is missing (also from the .diff): making it responsive as required by the spec.
The 3 steps together add up to the complexity of my patch.
Jul 6 2020
The latest patch was accidentally merged into the next patch in chain. To make review simpler, I've re-split the two.
Thank you, @Milimetric! Time to get it rolling 😃 Suggestions about how to prepare it are very welcome!
Yes, the above commit is from the master branch which is continuously deployed to BETA.
Patch 609806 (counter color not the actual):
Wrong task ID, patch belongs to other task.
In my understanding and deepest sorrow, typography questions in the Readers-Web-Team are lower than lowest priority. Comments suggest this will be the case while the Desktop Improvements project is running.
I'm interested in discussions and actual development in this area (demonstrated by my numerous Proof-Of-Concept patches), but I think "stalled" status and lowest prio expresses best the reality of this ticket.
If that's not the case, I'd be more than happy to see someone change it.
That's reasonable. Thank you for helping out with exact tag suggestion this time! Please keep that up in the future ;-)