New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 669256 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 849869
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 2
Type: Bug



Sign in to add a comment

RTL bugs in About page

Project Member Reported by shrike@chromium.org, Nov 28 2016

Issue description

Version: 57.0.2925.0
OS: macOS 10.11

What steps will reproduce the problem?
(1) Run Chrome in RTL mode (--force-ui-direction=rtl)
(2) Go to the About Chrome page

The Copyright string begins with a period. It looks like the period that should appear at the very end instead appears at the beginning. Same for the "Chrome is made possible..." string.

The Version string is messed up in a similar way: it looks like the close paren that should end the string has been placed at the very start of the string, and is an open paren instead of a close paren.

 
Screen Shot 2016-11-28 at 3.03.20 PM.png
86.0 KB View Download

Comment 1 by dbeam@chromium.org, Nov 29 2016

Cc: dpa...@chromium.org
Status: WontFix (was: Untriaged)
thanks for the bug!

I'm a bit leary of --force-ui-direction=rtl because it seems to be showing you a half-baked RTL UI.

using LANGUAGE={ar,he} on Linux is giving me better / more sane results.

also, punctuation should be flipped in RTL (so, on the left), so the periods are where I would expect.

I know it's a pain to flip your system language on Mac, but it's the only way I've gotten reliable results in the past :(

please re-open if you're sure there's issues and maybe show me locally with a full system language flip from settings?
2016-11-28-205019_1067x831_scrot.png
44.5 KB View Download
2016-11-28-205048_924x557_scrot.png
41.9 KB View Download

Comment 2 by shrike@chromium.org, Nov 29 2016

Status: Assigned (was: WontFix)
It is extremely easy to change the system language on the Mac.

Re: the punctuation, I was thinking that because it's a full English sentence within an RTL paragraph that LTR punctuation conventions would apply but apparently not. However, as you can see from the screenshot, the parens around the system version are still incorrect.

Screen Shot 2016-11-29 at 9.15.22 לפ׳.png
90.2 KB View Download

Comment 3 by dbeam@chromium.org, Nov 29 2016

Cc: -dpa...@chromium.org dbeam@chromium.org
Owner: dpa...@chromium.org
yep, this certainly seems like a bug if you've swapped language fully.  out of curiosity, is this string the same on beta/stable?

dpapad@: has this translation changed lately?  maybe the page isn't fully translated yet?

Comment 4 by dpa...@chromium.org, Nov 29 2016

Cc: dschuyler@chromium.org
@dschuyler: Is it possible that the "i18n{}" templating mechanism is messing up the version string? Printing the string in JS seems fine (see attachement).
version_rtl.png
60.9 KB View Download

Comment 5 by dpa...@chromium.org, Nov 29 2016

Labels: Proj-MaterialDesign-WebUI

Comment 6 by dbeam@chromium.org, Nov 29 2016

dpapad@: no, not likely
#4
The string is confusing the text layout engine (separate from i18n or loadTimeData). 

Since this is not a real sentence and instead a set of data about the version; I'll suggest setting dir="ltr" on this <span> so that it is *not* reinterpreted by the system laying out the text. Forcing the dir on the specific element will cause the text layout system to not change the layout of the text.

It may also help to align the text to the far left or right, depending on the actual dir. That way the unaltered string will be on the far left or the far right as appropriate.

Comment 8 Deleted

(Whoops it's a <div> not a <span>).
@dschuyler: Thanks for the suggestion. In fact that is what the old about page already does (see https://cs.chromium.org/chromium/src/chrome/browser/resources/help/help_content.html?l=18&dr=C).

I'll go ahead and make the same change for MD Settings.
So, adding dir="ltr" fixes the string itself, but messes up the alignment (see screenshot). Note that the old page already suffers from the alignment bug.
dir_ltr.png
85.0 KB View Download
Sorry, I think didn't explain this well enough, "It may also help to align the text to the far left or right, depending on the actual dir. That way the unaltered string will be on the far left or the far right as appropriate."

Using a css like
.foo-class[dir=ltr] { ... }
.foo-class[dir=rtl] { ... }

and wrapping the current div with something like:

<div class="foo-class">
<div class="..." dir="ltr"> ... </div>
</div>

Then foo-class would shift the text to the far right or left.
Status: Started (was: Assigned)
Status: Fixed (was: Started)
I believe this is fixed now. Please re-open if not the case.
Status: Assigned (was: Fixed)
Seems like it's still broken in the latest Canary?

Screen Shot 2016-12-07 at 4.19.52 אח׳.png
23.7 KB View Download
this is a pickle.

I would guess that there are no further code changes required by developers, and that when the translators actually finish the new translations (the SLA for that is only by *stable*), it should be fixed.

so basically, canary might be "broken" for a while, but it's likely only waiting on a translation (but it's not guaranteed the translation will have the correct directionality in each component of the translation).
Hm, this is not what I am getting on Linux see attachment.
rtl_version_linux.png
9.3 KB View Download
Mergedinto: 849869
Status: Duplicate (was: Assigned)
I believe remaining items on this bug are a duplicate of issue 849869.

Sign in to add a comment