Page MenuHomePhabricator

ContentTranslation creates erroneous "<g class" and "<grammarly-btn>" tags in article text
Closed, DeclinedPublic

Description

It looks like ContentTranslation is malfunctioning. See for example https://nl.wikipedia.org/w/index.php?title=Caquetio&oldid=52765249 .

Tags that seem based on article layout end up in the content of the article.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptDec 10 2018, 6:39 AM
Amire80 added a project: Upstream.EditedDec 10 2018, 7:00 AM
Amire80 added subscribers: kigorw, Amire80.

Looks like it's related to Grammarly.

If I'm right, then it's not the fault of Content Translation (CX), and I don't think that CX can do anything about it.

We already had a similar bug once: T124152. It was resolved by @kigorw, but looks like it, or something similar to it, came back. Perhaps @kigorw disabled it only for en.wikipedia.org? This bug is on nl.wikipedia.org.

These things should be done:

  • Translators who use Grammarly need to disable it while using CX. (Which is sad, because Grammarly is probably useful for writing.)
  • Either Grammarly should disable itself on Content Translation pages, or it shouldn't insert its markup in this way.
  • Important: This should also be tested with CX2, which has similar functionality, but uses a completely different editing surface. This can be done by logging in, going to https://en.wikipedia.org/wiki/Special:CX , clicking "Try the new version", and translating an article while Grammarly is enabled.
Amire80 renamed this task from ContentTranslation creates erroneous tags in article text to ContentTranslation creates erroneous "<g class" and "<grammarly-btn>" tags in article text.Dec 10 2018, 3:44 PM
Amire80 moved this task from Needs Triage to Upstream on the ContentTranslation board.
Pginer-WMF closed this task as Declined.Mon, Jan 20, 9:01 AM
Pginer-WMF added a subscriber: Pginer-WMF.

The new version of Content Translaiton (CX2) uses the same editing surface as Visual Editor so in case this issue still happens, it would be a more general issue (affecting Visual Editor) and not a Content translation-specific issue. So I'm inclined to decline this and create a more general ticket if there is confirmation of the issue to still happen.