Jump to content

Wikipedia talk:Redirects for discussion

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

"How to table..." unreadable in dark mode

[edit]

Having the cell colour of the How to list a redirect for discussion table hard coded to be white causes most of the text to be unreadable in dark mode, as the font colour is changed to a light grey. Dark mode is still in beta, and you can switch back to standard mode to make it readable, but thought it worth highlighting. Little pob (talk) 16:43, 21 August 2024 (UTC)[reply]

This seems to have since been fixed, but I'm still having dark mode problems for some archived discussions. For example, the text "Previous RfDs for this redirect and similar redirects:" is black text on black background on Wikipedia:Redirects for discussion/Log/2023 April 20#Chinese Transliteration Redirects to Korean People. After poking at this a bit, I'm still not sure what wikicode is generating that. -- Beland (talk) 06:43, 25 September 2024 (UTC)[reply]
That text is generated by {{Old RfD list}}. Thryduulf (talk) 10:07, 25 September 2024 (UTC)[reply]
Aha, the CSS for that template was setting the background color without setting the text color; I fixed it. Thanks for the pointer! -- Beland (talk) 15:36, 25 September 2024 (UTC)[reply]

Closure [keep/retarget]

[edit]

I find the phrase "Closure [keep/retarget]" in the heading of a section confusing, and wonder if it could be removed, changed, or hidden until there is actually a closure of some sort.

I was looking at one discussion at Wikipedia:Redirects for discussion/Log/2024 September 10 and almost didn't comment, because I saw what at first glance appeared to be a closed discussion; it was marked, "Closure [keep/retarget]". My first glance impression was, "Oh, this is already closed as 'keep and retarget'", but then it registered that "closure" is not "closed" and I wondered if that was relevant, so I scrolled around the page, and realized that every discussion had that phrase on it, so maybe none of them were actually closed yet, so I went ahead and commented.

Can we maybe change it to "Closure [   ]" while it is still active, and then update it later when it actually closes? Mathglot (talk) 21:14, 12 September 2024 (UTC)[reply]

@Mathglot those links are for enacting the closure, so hiding them until the discussion is closed would defeat the entire point of them. See, e.g. this revision to see the contrast between open and closed discussions. If others are finding the "Closure" wording confusing then I guess it could be changed to "close as" or something like that, but the current wording has been in place since 4 August 2011 and this is the first time (that I am aware of) that anyone has raised an issue with it. Thryduulf (talk) 17:48, 25 September 2024 (UTC)[reply]

Nomination for merger of Template:Rfd-NPF

[edit]

Template:Rfd-NPF has been nominated for merging with Template:Redirect for discussion. Watchers of this page are invited to comment on the discussion at the template's entry on the Templates for discussion page. Thank you. Steel1943 (talk) 22:16, 22 September 2024 (UTC)[reply]

How to simplify

[edit]

This page is WAY too complicated. Example: Trial (TV Series) is a BBC show from 1971. It has nothing at all to do with Goliath (TV Series). But, it redirects there. Why? Who knows. Can the redirect be removed? Maybe. Step 1: Spend the next two years of your life parsing through pages and pages and pages of instructions, most of which contradict with one another, to see if it is possible to put in a request to have the redirect removed. Step 2: You did it wrong. Try again. Step 3: You did it wrong. Give up. What should happen is Step 1: Easily state in one location that there is an invalid redirect. Done. No more work. Is that possible or is the primary purpose of this complicated mess to keep people from making requests? 12.116.29.106 (talk) 14:07, 2 October 2024 (UTC)[reply]

Hey there, perhaps the steps required to create a nomination could be simplified in the future, but at the moment the easiest solution to your problem would be to create an account and use the Twinkle gadget, which semi-automatically takes care of the back-end steps. You can ask at the Teahouse if you have any other questions about that, and an experienced editor will be able to help you out. TechnoSquirrel69 (sigh) 00:53, 3 October 2024 (UTC)[reply]

Crossnamespace

[edit]

Is Wikipedia:WikiProject Pokémon/Mr. Mime a proper redirect? Web-julio (talk) 02:40, 8 October 2024 (UTC)[reply]

Hey Web-julio, cross-namespace redirects are typically considered problematic if they go from article space to somewhere else and not necessarily the other way around. If you'd like the community to discuss this you can make a nomination for a full RfD. TechnoSquirrel69 (sigh) 02:44, 8 October 2024 (UTC)[reply]
checkY Closed WP:Redirects for discussion/Log/2024 October 16#Wikipedia:WikiProject Pokémon/Bulbasaur as Keep. Jay 💬 10:58, 27 October 2024 (UTC)[reply]

The redirect Wikipedia:Redirects for discussion/ has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2024 October 10 § Wikipedia:Redirects for discussion/ until a consensus is reached. cogsan (nag me) (stalk me) 12:54, 10 October 2024 (UTC)[reply]

Lint errors

[edit]

The process is creating lint errors. The reason is that there is a <includeonly></div></includeonly> included when you close discussion. But there is already a close div at the end of the discussion.

See this diff for an example manual fix. (IN this case the lint errors appeared in the "yesterday" page, where the page in question is transcluded today..)

I'd fix it myself, but I spend too much time chasing up things that people just wanna delete. All the best: Rich Farmbrough 18:50, 18 October 2024 (UTC).[reply]

 You are invited to join the discussion at Wikipedia:Village pump (policy) § Date redirects to portals?. Cremastra (uc) 01:42, 30 October 2024 (UTC)[reply]