In T384806#12015394 schreef @Jdlrobson-WMF:

In T384806#12015145, @Sjoerddebruin wrote:

@Jdlrobson-WMF I think this is good progress, although it will not be possible to use these as a value in math() etc, which can be quite useful in some situations.

Can you expand on this? https://gerrit.wikimedia.org/r/c/mediawiki/core/+/1300193 introduces CSS variables such as --image-size-standard. Would that do it?

Issue also reported on enwiki's technical village pump, can replicate it using Vector 2010. @Kipod, which skin are you using?

@Jdlrobson-WMF I think this is good progress, although it will not be possible to use these as a value in math() etc, which can be quite useful in some situations.

I have the same with Wikidata on both my personal and work laptop. I'm still logged in on other projects, but almost daily have to log in again on Wikidata.

Fixed.

Would love to fix this, but the script is unfortunately not hosted on Wikidata itself,

Fixed.

Last response six years ago, two users can't replicate it.

With the above applied:

I had this beta feature enabled this morning on nlwiki, I opt-in to new beta features in my global preferences. Sounds like a bug and I feel like that shouldn't happen (yet).

The current suggestions are now 4 years old and there is no sign of any successor system being deployed. Suggestions are an essential part of the Wikidata experience and it hurts to see it being handled like this.

In T197137#11820033, @Awesome_Aasim wrote:

On Fandom wikis, all sitewide CSS/JS requires approval by Fandom staff before it can be put live. We can do the same here.

User makes edit to sitewide CSS/JS -> user clicks "save" -> user prompted to reauth (either with password or with second factor) -> edit is not immediately live for all users until second and third user with (editinterface) permissions on separate IP address approves the edit and auths with their password and second factor.

For user scripts it would be: user makes edit to user CSS/JS -> user clicks "save" -> user prompted to reauth (either with password or with second factor) -> user script is live

Of course, a bypass would be possible through the loading of external scripts or sheets from a place like GitHub. But I highly doubt anyone would be able to load external scripts (except for vetted scripts) into site JS or CSS since the edit would almost certainly be rejected by the second interface admin.

Potential workaround for 1Password users: you can limit on exact domains https://www.1password.community/discussions/1password/autofill-behavior-when-only-fill-on-this-exact-domain-is-selected-hostport-match/103652

According to caniuse only Firefox seems to be the major outlier, the script could check if it's available/supported right?

In T416458#11588309, @Cparle wrote:

I'm boldly declining this. If people automatically dismiss the popup and never even find out that watchlist labels exist then the work on it was wasted.

Should clicking outside of them count as dismissal as well, perhaps after a number of times? Have been reading reports of users who expect that behaviour.

Looks to be the same cause as T404912.

I'm having this issue the last few weeks on my mobile Safari (latest iOS) while trying to comment on Wikidata, connecting it to my Mac shows "QuotaExceededError: The quota has been exceeded.". I don't think Safari allows deleting local storage for one specific website, but at the moment I'm unable to respond to messages on my iPhone using Vector 2022 this way.

We've discovered a lack of defaultsort's on the Dutch Wikipedia recently, some are from the ContentTranslation extension and were never resolved till recently (years to fix). Is there any update on this issue?

Most thumbnails are giving the following error:

Now it thinks it's a input field to login or create an account:

Seems to be a deliberate local change, see https://en.wikipedia.org/w/index.php?title=MediaWiki:Sharedupload-desc-here&action=history

My updated iPad does want to enter my credit card into it (giving me the option above the keyboard), my iPhone running iOS 18 only suggests me to add a credit card by scanning it. Both aren't blocking me like the macOS behaviour. I feel Apple did broaden the scope of what they see as a credit card field in the new version, probably due to low correct autocomplete value adoption.

In T401066#11150347, @Pppery wrote:

This isn't good:

Can each individual entry on a list be forced to stick to one column please?

The above patch fixes unexpected behaviour, like the parser profiling data table being broken in columns. I also made use of the less mixins instead.

Once again I had to correct a sitelink as the user never visited Wikidata. This should have been solved from the start of Wikidata, it's shocking this task still hasn't been solved.

Does the language used in the apps fall under policies of one specific wiki? It used to have an lower f for two years (it seems?), the F has been capitalised in 2017. Perhaps clear consensus about the sentence is needed.

I also wonder if they should use shorter texts, the contributions dropdown on the top-right also doesn't contain "Edit my preferences" in full.

All the inputboxes on https://commons.wikimedia.org/wiki/Commons:Bots/Requests, including the one to create a request, seem to point to MediaSearch now, any idea why that happens? Doesn't happen on for example https://commons.wikimedia.org/wiki/Commons:Oversighters

I feel the suggestions are now too narrow, especially with the last option being on two lines in multiple languages:

It seems the most recent Minerva change cut the bullet points on pages in half:

It's always up to a volunteer to make the current script more configurable, I don't think this needs to be declined. If it creates noise on the specific board just take it off the project.

What is the status of this task? Vector 2022 will be the default skin from next week.

Possible duplicate of T383047?

Still happening today:

This is breaking the workflow of tons of people and should get a higher priority or commits should be reverted as I don't see this fixed over the weekend.

Unknown date is an option I use frequently as it's hard to tell for logo's for example, would love a quicker way for experienced editors to indicate that.

Translators/scripts had almost no time to catch up with these changes, causing texts like "[⧼discussiontools-replywidget-reply-link⧽ Reageerfunctie]" to show up on group0 wiki's.

In T372702#10353445, @doctaxon wrote:

@Tgr: Wouldn't it be easier to recode the login and authentication routines or to revert to backups of the pre-August 2024 version? What is your opinion on that?