@bd808 yes, we do plan on getting a security review, per that task you mention above, as well as doing a first pass ourselves in T411130, but given the holiday train schedule, as well as the tight timeline for getting this to production in Feb. I'm just hoping to get the ball rolling on the release-prep process in order to make these tight timelines. 🤞

Confirmed with @jwang that this issue has been resolved.

LGTM, I don't see any visible changes as a result of this.

Confirming that the message is on translatewiki.net for translation
https://translatewiki.net/wiki/MediaWiki:Wikimedia-legal-safety-contacts/en
https://translatewiki.net/wiki/MediaWiki:wikimedia-legal-safety-contacts-url/en

This would be a good candidate for using Codex PHP (cc: @Catrope ) and I think we should implement some kind of server-side rendering for this page for a general release. Performance gets more problematic the more cards are loaded on the page (could be an issue for mobile app users who have lots of saved items). When rendering this page via JS, the browser looses the ability to do any preloading or preconnection for image resources and doesn't prioritize them the way it would if the cards were server-rendered.

I'm attaching screenshots of what I see on an iPhone 13 running iOS18.6.2. Even at very large text sizes, the search suggestions are legible on that device, so this bug may have been introduced in newer versions of iOS. I don't see a difference with reduced transparency either (wonder what's going on there, it looks like iOS is showing some kind over overlay when the keyboard is active).

@ATitkov Please file a ticket for the security review as normal, and we (Product Safety and Integrity) will expedite a decision (whether that's doing it ourselves, or deciding it's fine for you / your team to do it). We will make sure this launches on time.

hi @A_smart_kitten Ideally both, but I think any end-user reported bugs can be primarily filed with MediaWiki-extensions-WP25EasterEggs .

Just created MediaWiki-extensions-WP25EasterEggs. I'll tag the related tasks with both that and the PES1.3.3 WP25 Easter Eggs tags.

As Artem noted, this is a static HTML/CSS/JS site, and we don’t plan to update it after deployment unless absolutely necessary.

I'll verify on wide-screen monitor

hi @Dzahn, I just confirmed with @cmadeo that the desired domain/path for this microsite is actually:

Thank you all for addressing the "❌ ❓" in the comments above!