Sagang Wee

Yeah that is strange. Unable to repro on my side either. Does the test server have https://github.com/oppia/oppia/pull/15649 deployed?

Ah, I see the issue. Yeah the last user setting is stored in local storage in core/templates/pages/contributor-dashboard-page/contributor-dashboard-page.component.ts.

Yes sorry I meant to fix this by initializing the topic name to the first translatable topic name here: https://github.com/oppia/oppia/blob/develop/core/templates/pages/contributor-dashboard-page/contributor-dashboard-page.component.ts#L200, but I wasn't able to get to it this week.

Meant to fix this today, but am blocked on https://github.com/oppia/oppia/pull/15823 that fixes several UI bugs as a consequence of an Angular migration (the topic selector is not displayed currently).

Hey @qinghaoyang you might need to add a comment like "@{{reviewer username}} PTAL" for Oppia-bot to assign your reviewers for you if you're not a collaborator yet: https://github.com/oppia/oppia/wiki/Make-a-pull-request#step-4-create-a-pull-request

For current outdated translations, the user can't see the outdated translation.

Mocks can be found here: https://xd.adobe.com/view/2efbdf89-d293-4406-9720-77f77870093b-7ba8/screen/ef660789-fff0-4a80-95f1-a5a0d7afc00f

One way to implement this is to check if a translation opportunity has a matching translation suggestion with status APPROVED. This will require a lookup per translation opportunity however, so...

Design doc here: https://docs.google.com/document/d/1RIlefl2kmXyqwrcqTruNjJlQ6EWoiKs9DApT52Kahx8/edit#heading=h.liiqbmwmz8j8

We will handle obsolete suggestions differently in https://github.com/oppia/oppia/issues/16022.