In T321061#8564731, @Zm14 wrote:

I really feel bad about jumping the gun and misattributing the coincidental release of 16.3 and the unusually small POTD with the problem being fixed, even though I made it clear that I'd continue to check it wasn't just the smaller resolution. Since it's been days since my request for opening, I'll go ahead and reopen it back to Medium as it was.

@OTichonova Thanks for looking into the logic questions above.

PR (including test steps): https://github.com/wikimedia/wikipedia-ios/pull/4449

In T323473#8521358, @cmadeo wrote:

Per our tea time discussion:

• Let's aim to retain state as long as possible (eg. return user to their last opened article and depth whenever possible)
• For Open app on Search tab setting, respect this setting and always open to the search tab with the focus on the search bar (do not retain state)
• Deep links / quick actions / widget clicks will override state retention

In T321061#8508931, @Zm14 wrote:

I created the first report here, and it is definitely not fixed. Appreciate all the efforts.

Here's my current understanding of how the app's navigation/article state restoration works[1][2]:

Two big clean up tasks remain:

• Convert our remaining Core Data based widgets over to use the new self-sustaining data retrieval pattern that Feature Article uses. There seems to have been in increase in Core Data related SQLite file lock issues that manifest in multiple widgets of the same type on the home screen at the same time sometimes not working.
• Await feedback from Apple Radar about handling images in widgets. There seems to be new enforcement (but no documentation yet) in iOS 16 of image dimensions having maximum sizes in widgets, where exceeding that maximum size prevents a widget from archiving/rendering. We did some preventative work here that resizes POTD images to 1000x1000 max before displaying, but we need to revisit this if we get guidance or documentation from Apple.

https://github.com/wikimedia/wikipedia-ios/pull/4419

https://github.com/wikimedia/wikipedia-ios/pull/4417

Should be resolved as part of https://phabricator.wikimedia.org/T321061

Just wanted to drop a quick note from my current investigation and work on this so far if future Znuny emails come in: the behavior of images in widgets in the previous version of iOS 15 and the current shipping version of iOS 16 have indeed changed. This also explains why the widget gallery doesn't show a placeholder image for the POTD widget. This was unfortunately an undocumented change made by Apple in their OS and not made by us or communicated to us. The good news is we'll have a fix to address this behavior out in a future release of the app.

Our first objective on the engineering side before any potential logic change is made is to audit the existing work to confirm how it currently works and the potential flexibility we have.

Hey @ABorbaWMF, we made some design updates to this vanishing view. Before we ship, we'd like to do some very light regression testing of the view to be sure we didn't break any functionality. The part of the process you don't need to repeat is sending the actual vanishing email itself, but when you're able can you take a look at this on iPhone and iPad? I believe we'd like to prioritize this over other current iOS work as it's currently blocking our release of 6.9.4. The build in TestFlight is 6.9.4 (build 2000).

@OTichonova 6.9.4 (1998) in TestFlight now. In addition to your feedback above, also includes the keyboard show/hide button changes we discussed. When the user taps the Additional information field and the keyboard appears, the button stack disappears. When they finish with the field, the button reappears again. This is in both device orientations.

@OTichonova Updates are coming in an experimental TestFlight build (6.9.4) for you to review! There are some areas in which I had to fight the system's spacing, but if it's still not as expected let me know!

Right! I am with you now, sorry for taking so long to understand the ask.

@OTichonova No worries - sorry, I should have been more clear! Indeed you're right we use yellow50 as a value in app for different UI elements, but it doesn't seem like we have one specific semantic theme element (e.g. baseBackground, warning, etc.) that maps to using yellow50 as the value for each theme (light, dark, black, sepia).

1. Sorry, just to clarify, which background color are you referring to?

Currently, we're blocked on this. We're awaiting the trust & safety email address to use in-app.

Hey @OTichonova! Can you confirm the 1. background color and 2. theme element we should be using for the highlighted background shown here? https://phab.wmfusercontent.org/file/data/3nhdayomawj2dopfdjst/PHID-FILE-top6xydb3q2qiobmewwi/Search_primate_.png

In T311638#8308578, @OTichonova wrote:

Hi!
Doing design review for the empty states.

Remaining work in topic cells:

• Confirm RTL support
• Confirm VoiceOver support
• Confirm dynamic type support

Talk page engineering work needing updates after this work is implemented:

• Coffee roll container background color
• Talk page view background color

@OTichonova Do you have per theme colors available for the coffee roll background color?