Hi, in Vector 2022, if we want to select title of an article and we accidentally extend the selected area to select Table of Content button with the icon , then the text copied in clipboard would wrongly be (for example for the article "Wikipedia"):

Toggle the table of contents
Wikipedia

This is not the intended clipboard and the first line is not required, i.e., only "Wikipedia" as the title of the article is enough and the text "Toggle the table of contents" makes the clipboard data wrong.

The solution to this problem could be applying this style:

.vector-page-titlebar-toc {
  -webkit-user-select: none; /* Safari */
  -ms-user-select: none; /* IE 10 and IE 11 */
  user-select: none; /* Standard syntax */
}

I have tested that code in my css page at User:Hooman Mallahzadeh/common.css and it prevents this behavior very well.

Finally, I should note that this unexpected behavior in clipboard functionality is frequently occurred for me both in English Wikipedia and in Persian Wikipedia. Thanks, Hooman Mallahzadeh (talk) 04:30, 2 January 2024 (UTC)

Please file a task upstream. You do not need to support IE. You will also want to test with an accessibility agent or two. Izno (talk) 21:31, 2 January 2024 (UTC)

How to file a task upstream in case you don't know how to do it: Click here, fill it out, and tag it Desktop Improvements (Vector 2022). –Novem Linguae (talk) 23:59, 2 January 2024 (UTC)

I made a task for it at T354235. Thanks, Hooman Mallahzadeh (talk) 05:27, 3 January 2024 (UTC)

This edit request to MediaWiki:Minerva.css has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

Change "#0B0080" to "#795CB2"; the latter is the correct colour used on mobile Wikipedia (at least, as far as I can tell. This could be due to a specific preference on my account that I am simply not aware of) Loytra (talk) 10:58, 9 February 2024 (UTC)

 Done OK, note this is a short-term fix so let's not stress if the color isn't exact while waiting for phab:T356928 to be fixed. — xaosflux ^Talk 12:00, 9 February 2024 (UTC)

Not sure why you're implying I'm stressing? This was very much just a quick suggestion I made lol Loytra (talk) 13:45, 9 February 2024 (UTC)

@Loytra that was meant to be casual and general, not directly about you - in case anyone else wanted to debate the color shade further with the upstream fix appearing to be coming soon. Changes related to problems are welcome! — xaosflux ^Talk 14:34, 9 February 2024 (UTC)

I appreciate the clarification and apologise for making such a kneejerk assumption :) Loytra (talk) 16:03, 9 February 2024 (UTC)

 You are invited to join the discussion at Wikipedia talk:TemplateStyles § RfC: converting sitewide CSS to TemplateStyles. HouseBlaster (talk · he/him) 15:30, 21 February 2024 (UTC)

@media screen {
    /* Put a chequered background behind images, only visible if they have transparency,
     * except on main, user, and portal namespaces
     */
    body:not(.ns-0):not(.ns-2):not(.ns-100) .gallerybox .thumb img {
        background: #fff url(//upload.wikimedia.org/wikipedia/commons/5/5d/Checker-16x16.png) repeat;
    }

This is, apparently, being loaded for all pages on the English Wikipedia. While the PNG is only 81 bytes, it does necessitate that the browser make a second request to load the resource. This is kind of inefficient, deshou?

Instead, we could do this:

@media screen {
    /* Put a chequered background behind images, only visible if they have transparency,
     * except on main, user, and portal namespaces
     */
    body:not(.ns-0):not(.ns-2):not(.ns-100) .gallerybox .thumb img {
        background: #fff url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAAAAAA6mKC9AAAAGElEQVQYV2N4DwX/oYBhgARgDJjEAAkAAEC99wFuu0VFAAAAAElFTkSuQmCC') repeat;
    }

Now, //upload.wikimedia.org/wikipedia/commons/5/5d/Checker-16x16.png is 63 bytes, and data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAAAAAA6mKC9AAAAGElEQVQYV2N4DwX/oYBhgARgDJjEAAkAAEC99wFuu0VFAAAAAElFTkSuQmCC is 130, so we are adding another 67 bytes to the stylesheet, but we're eliminating an 81-byte PNG file, so overall we save 14 bytes -- and we also save the necessity of a whole extra request to load the PNG.

Right? Or no? jp×g🗯️ 04:10, 22 February 2024 (UTC)

Not 100% sure on upstream (including client-side) caching optimizations; suspect the PNG is more likely to stay cached there? — xaosflux ^Talk 10:18, 22 February 2024 (UTC)

I don’t know if any of them is cached longer, but there are multiple groups of people, and not everyone would benefit from the inlining:

• People who regularly visit Wikipedia (many people). They have everything cached, inlining wouldn’t matter much for them.
• People who read Wikipedia articles every now and then (most people). They currently download Common.css when they visit Wikipedia, and then don’t download the image, as the rule never applies in article space (browsers won’t download images just because they see them in the stylesheet). Their bandwidth usage would increase if the image was inlined.
• People who visit non-mainspace pages every now and then (relatively few people). They currently download Common.css when they visit Wikipedia, and then may download the image if they view a non-mainspace gallery. Their bandwidth usage may decrease (or increase, if they don’t view such galleries) if the image is inlined.

Given that the second group is far more populous than the third one, I think inlining the image would be a net loss. —Tacsipacsi (talk) 16:34, 25 February 2024 (UTC)

This edit request to MediaWiki:Mobile.css and MediaWiki:Common.css has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

Please add this to Mobile.css:

.mobileonly {
   display: inline;
}

and the following to Common.css:

.mobileonly {
   display: none;
}

While .nomobile is defined well outside of these files, .mobileonly (which is present in Fandom wikis) is not. This serves as a switch to allow content to be shown on mobile only while being hidden on desktop. Awesome Aasim 19:17, 20 March 2024 (UTC)

 Not done for now: please establish a consensus for this alteration before using the {{Edit interface-protected}} template. I don't see a reason for this. And moreover nomobile should also be avoided. If a specific element absolutely must not be displayed at a certain resolution, then it can use TemplateStyles and a media query. (Such cases probably honestly don't exist.) Ignoring both of those, Mobile.css's days are numbered. See the recent announcement in tech news. Izno (talk) 21:01, 20 March 2024 (UTC)

@Izno I am not finding where that information is. A link please? Awesome Aasim 17:52, 21 March 2024 (UTC)

Ah, not announced yet anywhere. phab:T248416 Izno (talk) 05:58, 22 March 2024 (UTC)

Plus, using the display: inline declaration to reverse the effect of a display: none is not always correct: the display: property allows several values, some of which are significant for structured block elements such as lists and tables. --Redrose64 🌹 (talk) 22:10, 20 March 2024 (UTC)

Pages should be written agnostic of what the browser will be. — xaosflux ^Talk 18:10, 21 March 2024 (UTC)

This edit request to MediaWiki:Minerva.css has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.

Replace

.flagicon img {
	min-width: 25px;
}

with

.flagicon img {
	min-width: 23px;
}

The default size for flag icons is 23px, so setting the min-width to 25px is causing all flag icons to be larger than they should be. This is problematic for Template:Flag data which takes advantage of the fact that 25px is 2px larger than the default size of 23px. Additionally, using 23px was the proposed fixed for phab:T116318. – BrandonXLF (talk) 18:43, 11 April 2024 (UTC)

 Done * Pppery * _{it has begun...} 15:36, 13 April 2024 (UTC)