Please I want to unsubscribe, because don't wanna receive more emails and
I'm blocked on WP. Thanks.

@santhosh
Is this issue repeat if you reload the page? Yes.
Is this issue happening only for a specific artcle or for all translaitons? This issue is happening for all translations.
Is this issue happening in a specific browser or for other browsers too? This issue is happening in Google Chrome (version 91, last version).

@Jdlrobson I don't like so much the deletion of the Mobile Frontend Categories Feature, but i like so much.

In T281739#7080907, @ngkountas wrote:

@RodneyAraujo could you provide some more information(source language, article title, section title) to reproduce this issue on Bengali Wikipedia, please?

@Pginer-WMF, @ngkountas: I saw that this error is also occuring on Bengali Wikipedia, at translating from english to Bengali

I saw that this issue is still occuring to me in mobile as in desktop, @Aklapper, @Pginer-WMF. This is really a bug.

@Pginer-WMF I have a question: When it's ready the support of Section translation on desktop? Thanks.

@Pginer-WMF The first enablement of the tool is now ready. See the following screenshots:

@Pginer-WMF, according to the specification image, the section header of the published section (Kasaysayan) is in serif font with bold weight, and the other sections, is serif font, with regular weight.

@Pginer-WMF On Spanish Wikipedia, the sandbox is known as “Taller” or “taller de usuario”.

@Pginer-WMF, also is missing that the section header of the published section must be in a serif font with bold weight.

The issue seems to be fixed.

@KartikMistry:
Ready in SX test server.

@Pginer-WMF That's some things that are missing: Is missing that after publishing the translated section, an transition effect should appear to scroll to the published section, and also other transition is missing to the invitation.

@Esanders, @Jpita, @Pginer-WMF: The issue seems to be fixed. See screenshot:

The change is now ready, @Pginer-WMF

And in desktop:

And this:

In T260139#6798193, @Jpita wrote:

2 issues:

• I can't make this work on mobile, this is what I see when I go to https://sx.wmflabs.org/index.php?title=Luna&sx-published-section=Estado%20legal

first screen	second screen after manual scrolling (no auto-scroll)

• if the title of the section has a space it also doesn't work https://sx.wmflabs.org/index.php?title=Luna&sx-published-section=Estado%20legal

New ticket or you'll fix it on this ticket @ngkountas ?

In T260137#6809766, @Pginer-WMF wrote:

In T260137#6809582, @RodneyAraujo wrote:

@Pginer-WMF, @ngkountas, when the messages of the invitation panel will be available on translatewiki for internationalization? Thanks.

The code for this is still in review. On the right column there is a "tags" section that shows the status of the ticket for the current work board "Language-Team (Language-2021-January-March)". Once the code is merged, you'll see that gerritbot adds a comment in the style of "Change XYZ merged by jenkins-bot...". Code needs to be merged and exported before it is available for translation.

Given that it is possible that, even after merging, some additional changes may be needed, I think the best time to look into translations is when the ticket is marked as resolved since all the checks will be completed by then.

@Pginer-WMF, @ngkountas, when the messages of the invitation panel will be available on translatewiki for internationalization? Thanks.

@Jpita @ngkountas @Pginer-WMF I've tried this in other mobile device and I saw that the "new" indicator is aligned to right. See screenshots:

In T260139#6798193, @Jpita wrote:

2 issues:

• I can't make this work on mobile, this is what I see when I go to https://sx.wmflabs.org/index.php?title=Luna&sx-published-section=Estado%20legal

first screen	second screen after manual scrolling (no auto-scroll)

• if the title of the section has a space it also doesn't work https://sx.wmflabs.org/index.php?title=Luna&sx-published-section=Estado%20legal

New ticket or you'll fix it on this ticket @ngkountas ?

I'm also have this issue in mobile devices.

In T273050#6791842, @RodneyAraujo wrote:

@Pginer-WMF I have seen that, instead of the text of the titles (Section by section and Suggested translations) must be aligned to left, the text is aligned to center. See screenshots:

@Pginer-WMF the change is now ready

@Pginer-WMF, I think that it is needed because "Translate" is one of the steps to expand articles, and thus, I'm talking of "Translate section by section".

And @Pginer-WMF, can you modify the text of the first step to include the "Translate" part before of "section by section"?

@Pginer-WMF I have seen that, instead of the text of the titles (Section by section and Suggested translations) must be aligned to left, the text is aligned to center. See screenshots:

but in other test, i've followed these steps and the translation is published correctly.

@KartikMistry i've cleared the browser's cache and i'm still having the issue.

In T244114#6784040, @Jpita wrote:

@Jpita can you confirm the issue is still there from your side?

weird, I followed the same instructions and didn't get the error.
let's wait for the deploy (next week since this week's train is blocked) and we'll try again to check if it's fixed.

@Pginer-WMF I don't like that the SX quick tutorial changed. I like more the previous version (Translating a new section is easy, quick and fun!) that this.

In T244114#6773485, @Jpita wrote:

@RodneyAraujo I tested this in production and it seems to be fixed, can you try on your end please?

i also experienced this, but using Google Chrome in a Samsung Galaxy A01 Core. See screenshots:

Step 1

Step 2

Step 3

Step 4

These are the steps to reproduce the issue:

1. Go to a Wikipedia page in a mobile device.
2. Scroll to end of the page and select "Categories" button.
3. Once that I've clicked on "categories" button, select the button "Add to a category".

Depending of the length of the page name, is possible that the "Publish" button, is not shown if the page name is too long.

And when I click on the second option, that is "Exit", it redirects to the published page, instead of redirecting to Content translation dashboard.

I saw that the published translation animation is more slowly than normal. In the moment of a pop-up appears saying if I want to leave the site, when I click in "cancel" option, the translation is not published and redirected to the page.

The change is now seen on Android

this also happens to me:

@ppelberg @RhinosF1 Apart of this, after clicking on publishing button and the button remains greyed out, when i reload the translation page or i open a saved translation, the templates are shown as the following:

In T252542#6672494, @Pginer-WMF wrote:

In T252542#6671474, @RodneyAraujo wrote:

I saw that the section translation publishing error messages, such as "your translation contains 100% of unmodified text" and "your translation cannot be published: contains 99% of unmodified text" is not translated to other languages on translatewiki.net. Can you fix and adapt these messages for the translation?

The UI messages are translated at translatewiki.net by volunteers, so these should become available in more languages over time. From your message it is not clear which is the issue you are pointing to: (a) messages not being available in translatewiki.net, (b) messages are available but they have some problems that prevent volunteers from translating them, (c) the massages are ready to translate but they have not been translated yet, (d) something else. Please let me know which is the problem you refer to. Thanks!

@Pginer-WMF I saw that in the section translation's test server, after publishing a translation of a section, the message that invites to the user to translate other section and the highlighted section is not shown. Can you resolve the issue? Thanks.

@RhinosF1 I've investigated the issue. The issue that causes to the "publish" button gets stuck on "Publishing" is caused by the templates, when it is inserted on the article.

I saw that the message to invite to the user to translate other section, is not translated to other languages. Can you adapt this message for translation?

@Reedy so only is a problem of the device, not a Mediawiki issue.

@Reedy can you reproduce this problem in a desktop device, with the mobile view enabled?

In T269614#6675179, @Reedy wrote:

Wiley Fox Swift 2X, Android 8.1.0. Chrome 87 also works fine..

It's probably worth trying to update your version of Chrome, along with any OS updates if available.

And also send feedback to Google via "Help & Feedback" that the page is locking up Chrome, as this seems more likely to be a Chrome/OS bug rather than a MW bug.

It is a fairly big page...

@Reedy I've experienced this in a Samsung Galaxy A50, Android 10, Google Chrome 86.

@Reedy Here it is the problems

Steps to reproduce the problem

In T269614#6675108, @Reedy wrote:

Please see https://www.mediawiki.org/wiki/How_to_report_a_bug. "it gets stuck" is not a useful bug report.

What is it? The mobile apps? Android? iOS? A mobile browser?

In T269614#6674626, @Reedy wrote:

What do you mean by "it gets stuck"?

Please see https://www.mediawiki.org/wiki/How_to_report_a_bug

I saw that the section translation publishing error messages, such as "your translation contains 100% of unmodified text" and "your translation cannot be published: contains 99% of unmodified text" is not translated to other languages on translatewiki.net. Can you fix and adapt these messages for the translation?

I have a question, when the Section translation will be avaliable on Wikipedia?

I've made drawings of the mobile design of ContentTranslation, specially, the Content Translation Mobile editor:

I'm having also the issue, see screenshots:

This is how it looks the Special: Content Translation in mobile currently.

this still happens to me

Recently I happen with the References in my recent translation, Segetibacter koreensis, from English to Spanish, some references is transcribed as <cite class="citation journal cs1">[https://www.uniprot.org/taxonomy/398037 "Segetibacter koreensis"]. ''www.uniprot.org''.</cite> instead of <ref>{{Cita web|título=Segetibacter koreensis|url=https://www.uniprot.org/taxonomy/398037|sitioweb=www.uniprot.org}}</ref>

In T265497#6576482, @Aklapper wrote:

Translate some article from English to Spanish (español),

In the future, please provide complete steps to reproduce and include links. I guess I have to

1. go to https://en.wikipedia.org/w/index.php?title=Special:ContentTranslation&page=Yellow%20soybean%20paste&from=en&to=es
2. click "Start Translation" button
3. scroll down to "See also" section in English article
4. Move the mouse over the Spanish article
5. Press "Añadir traducción"

Thanks.

In T266276#6575999, @Aklapper wrote:

Hi @RodneyAraujo, thanks for taking the time to report this! What makes you think that the problem has anything to do with the template? Also, can you please always include URLs/links to pages? Thanks.

This also happens to me

In T265497#6576000, @Aklapper wrote:

Hi @RodneyAraujo, thanks for taking the time to report this! Unfortunately this Wikimedia Phabricator task lacks some information.
If you have time and can still reproduce the situation: Please add a more complete description to this task. That should be

• a clear and complete list of exact steps to reproduce the situation, step by step, so that nobody needs to guess or interpret how you performed each step (how do you "try to add a template to your translation"?),
• what happens after performing these steps to reproduce,
• what you expected to happen instead,
• a full link to a web address where the issue can be seen.

Problems that others can reproduce can get fixed faster. Thanks!

@Jdlrobson recently i started a translation with content translation and the problem is that the text is not translated with MT

Regression: this problem that the "publish" (publicar) button of content translation get stuck on "Publishing" (Publicando...), still happens to me when I publish a page with templates in the content. Recently i tried to publish "OxIClean" (enwiki) to eswiki.

In T265657#6548606, @Pcoombe wrote:

I saw this briefly earlier (on Chrome 86) but not now. There's another report at https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Sidebar_shows_up_in_a_larger_font_than_usual which also says it's no longer happening.

@RodneyAraujo is this still happening for you?