Page MenuHomePhabricator

Trying to expand issues doesn't show content
Closed, ResolvedPublic

Description

When a template adapts partially a warning is shown, but clicking on the issue card to read it does not show it since the tool is not able to focus the input on the affected content.
See video for explanation of the issue.

Example based on:
http://cx2-testing.wmflabs.org/index.php?title=Special:ContentTranslation&page=Murder%20of%20Dee%20Dee%20Blanchard&from=en&to=es&targettitle=Murder%20of%20Dee%20Dee%20Blanchard

image.png (1×2 px, 413 KB)

Event Timeline

Pginer-WMF renamed this task from Content Translation Drop down doesn't show content to Trying to expand issues doesn't show content.Jun 21 2019, 11:06 AM
Pginer-WMF updated the task description. (Show Details)
Pginer-WMF triaged this task as Medium priority.Jul 12 2019, 7:07 AM
Pginer-WMF raised the priority of this task from Medium to High.Jul 29 2019, 11:49 AM

Change 531726 had a related patch set uploaded (by Petar.petkovic; owner: Petar.petkovic):
[mediawiki/extensions/ContentTranslation@master] Fix focusing of block transclusion nodes when their issue details are opened

https://gerrit.wikimedia.org/r/531726

Change 531726 merged by jenkins-bot:
[mediawiki/extensions/ContentTranslation@master] Fix focusing of block transclusion nodes when their issue details are opened

https://gerrit.wikimedia.org/r/531726

Using the article from the description, translating from english to esperanto, I managed to find this issue:

image.png (1×1 px, 305 KB)

Issues:

  • console error
  • number of "translation issues" is wrong (20/19)

Steps:

  1. Start a translation of the article and translate 20 or 30 paragraphs only using MT
  2. Using the arrows of the issues box, go through all of the issues until the last one
  3. click "Mark as resolved" on the last one (make sure the last paragraph has 2 issues, Missing reference and 100% MT usage, I used the paragraph after Suspicions of deceptive behavior

Uncaught TypeError: Cannot read property 'id' of undefined is already reported at T229230, but there was no clear way to reproduce. Now that we have one, the problem should be fixed over there.