Main functionality for the Translation view is already available, so we can resolve the ticket. There are some aspects to polish in follow-up tickets:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Today
Yesterday
Main functionality for the Confirm step is already available, so we can resolve the ticket. There are some aspects to polish in follow-up tickets:
Thu, Jun 13
Tue, Jun 11
Mon, Jun 10
Fri, Jun 7
Thu, Jun 6
I found some cases where reaching the Translation view through the UI results in an UURL that when reloading the browser page shows a blank page with JS errors. For example: https://ca.m.wikipedia.org/wiki/Special:AutomaticTranslation?page=Plants+in+space&from=en&to=ca&display=en&step=translation
Wed, Jun 5
Tue, Jun 4
Mon, Jun 3
I noticed the issues may still be happening, although in a way that is harder to notice. The video below shows how the "Twin" article is selected, and the initial language pair is changed from " "Afrikaans to English" to "English to Spanish".
When the Translation View is accessed all UI elements seem to indicate that we are viewing the "English to Spanish" translation. However, the contents displayed are from the Afrikaans version of the Wikipedia article (note the difference in number of sections and images present in the English version )
I tried to check this. The dialog was shown, but there was no spitting of sections into their own drafts:
In T364621#9845813, @ngkountas wrote:
- page (title of the page in display language)
- display (language in which the search result is being displayed. Also the language in which the page title is provided in the URL)
In T366149#9841263, @KCVelaga_WMF wrote:@Pginer-WMF I have identified the events mentioned in the task description as priorities for the next set of events to be instrumented. Please review and if you think something else should be prioritized to understand user interactions, we can discuss.
Fri, May 31
In T363183#9820849, @ngkountas wrote:@Pginer-WMF my understanding is that once we deploy these changes, the mffrequentlanguages entrypoint (i.e. the missing languages banner entrypoint) will be removed from the CX/SX instrumentation. Since, we now navigate the user to an intermediate step (the overlay where the new entrypoint cards are displayed), it will be hard to implement such instrumentation. Is my understanding correct?