For Hindi language,Text appears to be chopped in pages section of print preview.
Reported by
mni...@etouch.net,
Jun 1 2016
|
|||||
Issue descriptionVersion: 51.0.2704.78 394fe3178d37c1aeae609094278643adbc222c55-refs/branch-heads/2704@{#688} (32/64-bit) OS: Windows (7,8,8.1,10) What steps will reproduce the problem? 1) Launch chrome, go to chrome://settings and click on Show advanced settings link. 2) From Language section, change the browser language to Hindi and restart the browser. 3) Now open NTP and press 'Ctrl + P' from keyboard to print and print preview will appear 4) Now go to pages section and click on custom input text box and enter any invalid text,observe अमान्य पृष्ठ श्रेणी text Actual : अमान्य पृष्ठ श्रेणी text is seen chopped Expected : अमान्य पृष्ठ श्रेणी text should be seen properly This is a non regression issue seen from 'M-30' series.(Build : 30.0.1549.0) Note : Issue is not seen on Mac and Linux OS.
,
Jun 1 2016
Able to reproduce the issue on win8.1 chrome version 51.0.2704.78
,
Jul 7 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 14 2017
,
Apr 4 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/edde5cf5f6805ca0396c763aa4a6ba807c804153 commit edde5cf5f6805ca0396c763aa4a6ba807c804153 Author: rbpotter <rbpotter@chromium.org> Date: Tue Apr 04 20:46:15 2017 Fix Hindi language print preview cutoff Remove the line height parameter in the hint CSS so that the text is no longer cutoff in Hindi. The hint shows if there is an invalid value in pages (or scaling or copies). BUG= 616372 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation Review-Url: https://codereview.chromium.org/2795123002 Cr-Commit-Position: refs/heads/master@{#461825} [modify] https://crrev.com/edde5cf5f6805ca0396c763aa4a6ba807c804153/chrome/browser/resources/print_preview/print_preview.css
,
Apr 5 2017
Tested the latest Canary (59.0.3063.0) in Windows 10 and the CL from comment 5 seems to have fixed this issue for me. Please verify.
,
May 26 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by mni...@etouch.net
, Jun 1 2016