XTools is down: https://xtools.wmcloud.org/ec/enwiki/ I assume it's related to this? cc @MusikAnimal

Perhaps it'd be better to let our people work on this (WMF Moderator Tools team talking to their contact at Newspapers.com) instead of Wikipedia Library users interfacing with Newspapers.com directly. Interfacing with them directly might just confuse and bother their customer service reps.

In T344534#9208024, @stjn wrote:

I also don’t think that WikiHiero should be undeployed without providing an alternative solution first. Just converting the text to Unicode is not a solution, developing a Lua module/template that would insert the approximately same markup is a better one.

Or figure out a way to keep the bright color and still achieve the contrast requirement. Perhaps by changing the font color of the text.

I am no longer able to reproduce this. Thank you for the quick patches. Can probably mark this as resolved, but will let the machine learning team make the decision on that in case they want to track it on their kanban board.

In T347367#9198439, @taavi wrote:

PetScan has also a separate issue: T347317: petscan expects javascript function callback from ORES

I confirm this bug on enwiki in the user script https://en.wikipedia.org/wiki/User:Evad37/rater, which has 1200 installs. The CORS error is:

Sounds good. I went ahead and did a strikethrough of "functions to classes". You can add to your maintenance backlog now if you want.

Thanks for the bug report. This one happens to be a duplicate, so I will merge this ticket into the older ticket.

I think a Toolforge tool is a close enough fit. Don't think this idea that it's not a userscript or gadget needs to be a blocker.

The legend should probably say something more specific than "closed". I assume "closed" means "read only, not accepting edits". We should probably verify by reading the code.

Marking as declined for now to reflect reality. When myself and the NPP team did a big push to implement this in 2022, various folks had small objections that added up into enough objections to stall this. No reason to work on it if it's just going to get stalled. We will focus our energies elsewhere for now.

Your sandbox renders like this for me. Chrome 116, Windows 10

Ah OK, so the GetPreferences hook lets us make a "normal" preference rather than a userjs- preference, which has some advantages. Got it.

Yes, I see localStorage in a code search of the repo, so it is probably also saving to the browser.

BC logic

Still happening as of May 2023. Is intermittent, not consistently reproducible, but I've noticed it multiple times. See T335832: Sometimes visiting an old diff marks all revisions for that page as read in watchlist for some screenshots and notes.

Looks like the save code is...

Can you elaborate a bit more on what the problem is with userjs, what the advantage of the GetPreferences hook is, etc?

Thanks for taking a look at this.

Thanks. I filed T345685: On first visit to Quarry in that browser session, error 500 (intermittent)

I forget which ticket I originally shared my concerns in, I think I made a post about this. But I am worried that mw.util.addPortlet() is not generating HTML that is similar enough to the skin that it is being used in. Ideally each skin would be able to specify what kind of addPortlet() HTML is generated, and that HTML would be identical to other HTML portlet code used by that skin.

Had my issue happen again.

Thanks for the quick turnaround! Does it just need some localhost testing?

We discussed this a bit offline. Here's some ideas:

@MPGuy2824 has done some work on the Special:NewPagesFeed mwe-vue-pt-info-pane and may have some thoughts about flex vs grid vs tables.

I did some tests just now, and recent patches have fixed the "reduction in the number of visible rows" issue and also the padding issue. Should be OK to close this one as resolved.

The "able to type into text box" part of this is solved. The "radio button should be selected" part is covered in T345154: In Vue.js NewPagesFeed, selecting Username filter text box should also select the radio button. Closing.

May need more work. The shadow correctly disappears when you switch filters from a list with a lot of items to a list with zero items, but when you scroll up, the shadow prematurely comes back.

Unexpected whitespace between radio button and text box on beta cluster. "Username" doesn't display at all. May need more work.

https://gerrit.wikimedia.org/r/c/mediawiki/extensions/PageTriage/+/951550 merged on August 22