Work for the user experience of the Abstract Wikipedia project.
Details
Yesterday
Needs some thinking about what we actually want the user to do in these cases, and how we can help them make it happen without crashing their browser.
We should probably just delete these?
We have this feature built last year, but unfortunately it broke the system so we 'temporarily' disabled it. I'll merge this task in with the main task about re-enabling it.
Change #1212533 merged by jenkins-bot:
[mediawiki/extensions/WikiLambda@master] MetadataDialog: use default component in Metadata dialog for displaying expected/actual values
Wasn't aware of it. Ok then let it be in its original position. We can close this ticket.
I think (but Joydeep should correct me) In codex theres a footer like this:
@JSengupta-WMF could you elaborate?
Ah now having a more thorough look indeed its new ideas (I kinda stopped with some tickets just by seeing 2023 and scanning, so my bad if some were flagged wrongly [400 tickets was a lot haha])
Hey @gengh ,
What is the difference between Abstract-Wikipedia-Digital-Garden and the "Design Backlog" column? I mean, potentially (or ideally), all the tasks on the Phabricator board that aren't bugs or problems are potential ideas for the future, just flagging this with Design tag (which already has) and moving to the Product/Design Backlog would be enough?
Tue, Dec 2
Change #1211643 merged by Jforrester:
[mediawiki/extensions/WikiLambda@master] Replace our use of Intl.RelativeTimeFormat with the convenience wrapper mediawiki.DateFormatter now it exists
The concurrency errors given by the stampede of renderer function calls at once is fixed.
Thanks @99of9, I'll be closing this task now.
I'm going to voldly claim this is fixed, yes.

