Page MenuHomePhabricator

RTL issues in ContentTranslation article selector and dashboard
Closed, ResolvedPublic

Description

Found in wmf.13 hewiki

  1. Misplaced parentheses in the list of search suggestions

Screen Shot 2017-02-24 at 11.48.45 AM.png (434×764 px, 96 KB)

Another, more complex example for misplacing forward slashes:

Screen Shot 2017-03-30 at 3.32.03 PM.png (573×903 px, 125 KB)

[non-reproducible] 2. Several examples when the article excerpts phrase is repeatedly dislayed.

Screen Shot 2017-02-24 at 11.46.56 AM.png (132×925 px, 44 KB)

Screen Shot 2017-02-24 at 11.44.03 AM.png (333×878 px, 101 KB)

  1. [minor] the drop-down menu box is not quite aligned:

Screen Shot 2017-03-30 at 3.30.30 PM.png (363×869 px, 47 KB)

Screen Shot 2017-03-30 at 3.26.52 PM.png (452×509 px, 44 KB)

Compare with LTR:
Screen Shot 2017-03-30 at 3.30.07 PM.png (459×1 px, 69 KB)

Screen Shot 2017-03-30 at 3.28.36 PM.png (458×432 px, 39 KB)

Event Timeline

@Etonkovidova : Please associate code projects to tasks - thanks! I assume this is about the ContentTranslation extension.

Amire80 renamed this task from [minor] RTL issues to RTL issues in ContentTranslation article selector.Mar 6 2017, 8:09 PM
Amire80 added a project: Essential-Work.
Amire80 renamed this task from RTL issues in ContentTranslation article selector to RTL issues in ContentTranslation article selector and dashboard.Mar 6 2017, 8:16 PM

In issue 1, the parentheses is just a symptom. In Firefox the parentheses would probably have correct appearance. But the real problem is that the article names don't have the direction of the language. The mw-cx-ui-PageSelectorWidget element must have the same lang and dir attributes of the language that is selected.

I couldn't reproduce issue 2, but it's a bit hard to do on a screen that shows something different time :/

Yes, #2 is not reproducible - might be just temporary issue with fetching article description.

I'm closing this:

  1. Is an upstream bug, as explained above.
  1. Not reproducible.
  1. No longer relevant because of the dashboard redesign. T114097 is somewhat and still relevant, but already reported separately.
Amire80 claimed this task.

Forgot to mention: The slashes issue is not a CX problem, but a content formatting problem. There should be a global unified way to format code examples on all wikis, and it should include correct code direction setting.