User Details
- User Since
- Apr 9 2015, 4:16 PM (414 w, 6 d)
- Availability
- Available
- IRC Nick
- Izno
- LDAP User
- Unknown
- MediaWiki User
- Izno [ Global Accounts ]
Today
Looks to have been added for T149809: [A/B Test] Add 'explore similar' pages, categories and suggested languages in search results.
Tue, Mar 21
Thu, Mar 16
Per fix onwiki.
Tue, Mar 14
There's about 400 articles on en.wp with that pattern.
Sat, Mar 11
My opinion on whether to do user scripting separately is that we can bite the bullet now or we can bite it later. It will be a much bigger bullet later. The longer you allow the assumption to bake in, the worse it gets, and TBH it's one reason Vector should never have been loaded with Vector 2022. During 'beta', migrating could have been done essentially without any user cost, as with the previous transitions. "Nothing is loaded from your old pages, copy-paste CSS changes to the new CSS page and preferably move any JS customizations to your common.js, but copying to Vector-2022.js will suffice." (My opinion is that JS shouldn't be a skin-specific quality in most cases.) That cat is out of the bag now and waiting isn't going to help.
Wed, Mar 8
As framed, this issue cannot be resolved by work done in the core software indeed, and the correct place to discuss improvements is https://en.wikipedia.org/wiki/Module_talk:Footnotes . (Which may necessitate some core software change, but I doubt it. Ttm is pretty savvy about what can be fixed in the core software.)
Tue, Mar 7
I added T313804 as a subtask because it appears to be basically done on this work.
Mon, Mar 6
Sun, Mar 5
I was planning to file this task when there was a greater percentage of views supporting them and when they were no longer at working draft.
As a side note after the dupe close, the p tag in HTML does not match exactly to our notion of a paragraph these days. It's more structural. So I agree with two separate p elements before and after.
Fri, Mar 3
Thu, Mar 2
Wed, Mar 1
Tue, Feb 28
Doesn't appear so based on a cursory review of UniversalLanguageSelector .
Sun, Feb 26
Use ?uselang=qqx to get the message name associated with a string on an arbitrary page.
Sat, Feb 25
Tue, Feb 21
Feb 21 2023
Based on my read of this change and a request for help on IRC today, this narrowed the allowed type of the configuration global from string or array of strings to array of strings (the cast to array looks to have been removed), and probably should have been documented in release notes/announced accordingly. https://www.mediawiki.org/wiki/Manual:$wgSpamRegex 's example(s) is/are out of date as a result.
Feb 19 2023
Feb 18 2023
Right, "I also know that seems like a lot of work."
Feb 17 2023
Feb 16 2023
See response on T329809: [ reply ] button shows up for comments in tables.
I have a feeling that comments in tables was probably requested at some point to respond to barnstars, wikilove, and other such messages, many/most of which are today implemented as tables.
Going to unmerge this. The other task could potentially be declined as recently discussed, and I didn't realize when I made the comment in T300919#8276491 what the context of the statement was and what the specific intent was, which does look different enough from this task's intent. I don't think implementing the other task would resolve this one reasonably, based on the acceptance criteria therein.
Feb 14 2023
Feb 13 2023
Feb 11 2023
Ahhhhh clicking the wrong thing (first word in the header). Yup, I can repro now too.
Are you sure this is a DiscussionTools problem? I can't replicate on WP:VPT in Firefox 109 with DT turned on, which Matma Rex seems to think it will be a problem on that page. :) (Double clicking gets me the word and the space after, which is expected behavior.)
Feb 10 2023
Feb 8 2023
Reasonable concerns. OTOH, right now the "bad" edge case is NavPops. I bet we can enumerate the problematic gadgets on one hand for gadgets that actually need something of this sort. Separately, the bad cases probably need these fixes regardless. As a particular example of an edge case, I believe NavPops doesn't check today for the general user ability to hover and should, so that's a check that needs to be added regardless of whether it's loading on mobile or desktop, because neither of those two targets do that today. And then this problem is solved for that gadget, since it shouldn't be judging mobile use based solely on the domain or skin it's on. As I suggested above, that's a check that probably could/should be added to mw.util or other library. I don't think it could be done in the definition, especially since I could go from tablet-without-mouse to tablet-with-mouse pretty easily (as a particular example).
Feb 7 2023
I agree.
Not really sure why you pinged Xaosflux, but he's as good as any to have subscribed. :)
Yes, the skin potentially doesn't support gadget X that user Y expects to work. I would rather, as I have now said multiple times, affirmatively add a statement that says "this gadget works in this skin", along with the assessment that would likely be done for all gadgets at the same time, and tell the users "yes, gadgets aren't assumed to work in a new skin", than have the converse discussion "the gadget doesn't work for this skin", "yes, that's because the gadget is broken".
There are default gadgets on multiple wikis that in fact load for everyone.
Feb 5 2023
NavPops is a hard question to me, I think, and worthy of thought regardless. Popups extension too, I wonder what that one does today for systems where the normal mode of use is touch. (Consider that if I really wanted, I could manage to use a mouse with a phone. SO has an interesting comment.)
Feb 3 2023
side effect of a trick that the table does
@TheDJ well of course the fact we're cheating is causing it. :) (It's not the only one specifically tied to the cheat that's shown up in the past few week, had to back and forth with Matma for the display-the-lead talk page work.)
Feb 2 2023
Feb 1 2023
The root issue is T281974: Fix alignment of coordinates and page indicators (Vector 2022).
Jan 30 2023
It's not just pre. An image with the appropriate wide image template as explicitly recommended doesn't fix the issue. I left this on another task discussing an issue in V22 but since you think it's one cause, it's not. https://en.wikipedia.org/wiki/Sixth_Amendment_to_the_United_States_Constitution?useskin=vector-2022 with limited width turned off exhibits the same issue.
Jan 29 2023
Jan 28 2023
Yes, intentional for separating rows. Most questions using SecurePoll probably have more than one response e.g. ArbCom elections.
Yes, this is a known issue from several years now. Should just be
Related to T327886: Long string of characters comes out of the body content and overlaps the Article tools menu in Vector 2022 and other related tasks there.
Jan 27 2023
Jan 26 2023
The display of https://en.wikipedia.org/wiki/Sixth_Amendment_to_the_United_States_Constitution?useskin=vector-2022 with the toggle set to "wide" but with any reasonably sized monitor resolution probably needs to be of interest here.
I've actually been coming to like the idea behind Zebra 9. It tends more toward how Timeless does its sidebar and main column support in that like Zebra 9, we're shooting for bounding the reading area, not "almost" bounding the reading area as in Blue whale. Even if the right toolbar becomes sticky, it may still not be full height relative to the main content.
This is still missing the span. If there is a reason not to add the span, that's fine, but that was not documented in this task and should be if it's deliberate.
Jan 25 2023
This is a special case of T66577: Large tables created by editors are not responsive and would be as fixed as it needs to be if that were resolved. In the meantime, this is one place the software could take care of the issue in some way, such as with
This is functionally a duplicate of T319387: Random <i> tag wrapping .mw-content-container in Vector-2022.