User Details
- User Since
- Jan 30 2019, 8:58 PM (286 w, 2 d)
- Availability
- Available
- LDAP User
- Unknown
- MediaWiki User
- Nardog [ Global Accounts ]
Wed, Jul 24
Turns out anon/!anon/hideanons already work in watchlist and feedrecentchanges.
Does this task also cover ApiQueryWatchlist, ApiFeedRecentChanges, and ApiFeedWatchlist?
Tue, Jul 23
ApiQueryWatchlist, ApiFeedRecentChanges, and ApiFeedWatchlist also have anon/!anon or hideanons options.
Mon, Jul 22
Fixed, the double negative failed me.
Sun, Jul 21
Mon, Jul 15
Sat, Jul 13
Thu, Jul 11
Wed, Jul 10
@Jdlrobson How can I reliably do that? The radio buttons are created client-side. It also feels ridiculous to have to essentially reverse what a script has done instead of preventing it from running in the first place.
@Jdrewniak That defeats the primary benefit of a dark mode gadget, which is that you don't get FOUCs.
Tue, Jul 9
Sounds good.
Mon, Jul 8
Thu, Jul 4
Now the CSS has a rule for .damaging.damaging.mw-changeslist-damaging-verylikelybad, with two .damaging, which thus overrode my custom CSS.
Wed, Jul 3
No, just give me an option that's basically "I don't care if they interfere, just enable these radio buttons" because (1) the toggle gadget alone doesn't interfere in any way whatsoever and (2) the dark mode gadget can be disabled without reloading.
Tue, Jul 2
The gadget is not compatible with dark mode, so I'm not exactly sure what you expect to happen here. We can't enable dark mode while the gadget is present in the page.
This has made fixing things for the native dark mode really difficult. I want to continue using the gadget, but I can't test the native dark mode with just useskin=vector-2022. I want to help you, so please don't make doing so difficult.
Jun 26 2024
Also happens on links:
Jun 22 2024
I don't understand why "background-color-content-added" and "background-color-content-removed" can't use different shades of the same colors as "color-content-added" and "color-content-removed" (i.e. green and red), just as "background-color-success-subtle" and "background-color-error-subtle" use lighter shades of the same colors as "color-success" and "color-error".
Jun 20 2024
Jun 16 2024
Possible duplicate of T207383: Inherited methods and members of mixins are missing
Jun 10 2024
Jun 8 2024
How is this different from T363630: Score audio cannot be played if the page has other embedded media?
Why are we defining SpinnerOpts and TableSorterOptions as separate types? confirmable(), highlightText(), makeCollapsible(), suggestions(), etc. also accept options through an object, but they're not defined as types. As a reader I prefer the available options to be documented inside the same section as the method that accepts them rather than having to scroll back and forth.
Jun 6 2024
Why not fire the wikipage.content hook for the ref content?
If ReferenceTooltips copies elements preserving handlers using jQuery, the problem is simply that Phonos uses not $.fn.on() but addEventListener(). If Reference Previews does not preserve handlers, switching to $.fn.on() will not be enough to solve the issue. They seem to require different solutions.
That task is about Reference tooltips, not Refernece Previews.
As evident in hastemplate, "links" in linksto is the third-person singular verb, not the plural noun. linksfrom wouldn't make much sense.
May 30 2024
rewrite the documentation using typedefs describing the options for each of the commands.
That would not be sufficient because any callback added via register() should behave the same way as its default counterpart, i.e. accept the same options and return the same expected value. Not just the options but the methods overall need to be documented.
May 21 2024
May 18 2024
May 15 2024
May 11 2024
No adequate explanation given why this can't be addressed in MFE.
May 10 2024
Would we enable notifying others in production?
May 7 2024
Something along the lines of "If you have 'Show preview without reloading the page' on in your preferences, now 'Preview page with this template' also works without reloading the page."
May 4 2024
@MusikAnimal Thank you so much for the review!
May 1 2024
@Jdlrobson If MobileFrontend meddles with "which skin to display" then it absolutely has to do with this. If it gives you Minerva regardless of the skin preference, then why can't it also override the responsive preference? What's the point of a for-mobile site that doesn't have width=device-width anyway?
Apr 29 2024
I thought the fix for this task might fix T363630: Score audio cannot be played if the page has other embedded media too, but that one is still happening so apparently not.
Not reproducible anymore.
No, it does not behave as expected because Minerva is the skin you're going to get no matter the preference. The responsive mode toggle should be accessible so long as MFE is installed.
This is annoying because now you can't toggle responsive mode for mobile unless you change the desktop skin. Filed T363674.
Apr 28 2024
For one, it has to be styled basically from scratch to blend with text and not look like a button. And it would have to be inserted (or enabled) client-side.
Now called Asahi Shimbun Cross-Search.
https://xsearch.asahi.com/
Seconded. Having Scribd in the collection will likely make it more difficult to court more reputable publishers.
I was just explaining why it works in your first example and it doesn't in the latter. The presence of other embedded media on the same page triggers the use of the VideoJS player for Score-generated audio.
Somehow, the same code works here but here doesn't
Apr 26 2024
Apr 22 2024
Apr 19 2024
Apr 16 2024
Not sure what still needs to be done about this technically. The deprecation of the old module can be done by volunteers on wiki.