I think that all issues on this ticket have been resolved. Please take a look at the screencast: https://imgur.com/a/IMksGBV

Cool! @Pginer-WMF In that case I think we can close this ticket as resolved as the second issue @Jpita referred is being addressed here: T262665: on mobile we can't see the button to skip the tutorial

@Jpita Do you find the initial issue to still be existing? I've checked on test server, Chrome mobile emulator for iPhone 5/SE and I could scroll the page as expected.

@Pginer-WMF I have created a new ticket concerning the first of the points you made above (i.e. Selecting the section title is not possible) here: T265220: Pick a sentence: Section title should be translatable. Given the fact that the other two issues have been addressed here in separate tickets (T263940: Pick a sentence: Fix content reflow on sentences that follow highlighted sentence, T260129: Pick a sentence: Feedback when tapping on selected sentences), I think we can close this ticket as resolved.

@Pginer-WMF I agree on every point you made. Fixed issues according to these points in related patch.

In T259496#6498253, @santhosh wrote:

Got it. So can't this be solved if the default UI of tab in our vue UI library follow grey underlines instead of following OOUI style? @ngkountas If we do that, then we don't need customizations right? The tabs we have in desktop dashboard will also follow the grey underline style.

In T263718#6490298, @Jpita wrote:

I have a feeling this will appear more times throughout the app, can @ngkountas or @santhosh tell us why this is happening?
Is it like a default state for the component that then gets updated? if that's the case we should think about setting the default to a loading gif or something so that doesn't happen

In T259506#6484119, @Jpita wrote:

So the inspector being cropped in the first example is more an artifact of viewing the desktop version on a narrow viewport. I think this is more for the Editing team to consider whether to make use of the mobile format on narrow screens (not only based on device). If we found the issue affecting our users in any way we can ping the Editing team or explore alternatives. For now, I don't think we need to do anything in this front.

according to your spec

The standard Mobile Visual Editor will be reused

right now is not because is not the same.
is this not something we need to fix on our end on this task?

@ngkountas can we fix the js error on this task?

In T259497#6473881, @Pginer-WMF wrote:

The "open in new tab" icon was intended to be using Base30 color (#72777d). However, it is shown in black currently which gives more visual weight than intended.

@ngkountas, is this something easy to adjust or the icon system needs more general improvements for allowing icons in different colors?

@Jpita Jumping in here to help with some clarifications so that it's easier for you to monitor things (@Pginer-WMF please correct me if I'm wrong): Pau has already split this ticket to remaining subtasks and since this is not a huge ticket, I believe that the only things to check for this specific ticket (excluding child tickets) are paddings/margins, colors and font-sizes for translation options (original sentence, google, yandex, empty sentence etc) and card header titles. Everything else is already captured in newly created tickets by Pau.

@Jpita Edit translation button should work right now. Visual editor loads slowly but should be visible after a while:

Sure. "New section" banner appears in two cases: 1. Compare contents step: Choose "Full article in {targetLanguage}" content. It should appear at the end of the article if you scroll down to bottom. 2. Compare contents step: For a mapped section (present/already translated section) choose "Section in {targetLanguage}" content. It should appear at the end of the section.

This is a specific issue of this step and doesn't affect other screens. Follow-up ticket has been created: https://phabricator.wikimedia.org/T263118

Improvements on this ticket have been stalled for now. We'll come back to this later, this is why the ticket was moved to Quarter Backlog again.