Issue metadata
Sign in to add a comment
|
Regression:'Search cookies' ghost text is seen chopped after changing browser language
Reported by
nutan.ga...@etouch.net,
Jun 14 2017
|
||||||||||||||||||||
Issue descriptionChrome Version: 61.0.3130.0 34174075ba5fe272eb1666f4d04857cadc24a83d-refs/heads/master@{#479232} OS: Windows(7,8,8.1,10). Steps to reproduce: 1.Launch Chrome, navigate to chrome://settings/languages, change browser language to 'French(Canada)' 2.Relaunch chrome, go to chrome://settings/appearacne and change Font Size to 'Very Large'. 3.Go to chrome://settings/privacy and click on Content settings > Cookies and observe the 'search cookies' ghost text in search box Actual: 'Search cookies' ghost text is seen chopped after changing browser language Expected: 'Search cookies' ghost text should not be seen chopped after changing browser language This is regression issue broken in 'M 59' and will soon update the bisect info: Manual Bisect Info: Good Build: 59.0.3051.3 Bad Build: 59.0.3053.0 Note: Issue is not reproducible on MAC and LINUX OS.
,
Jun 14 2017
,
Jun 14 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0a9fd735b58bf6fe1a7eb2b9d743dc65650afc02 commit 0a9fd735b58bf6fe1a7eb2b9d743dc65650afc02 Author: dpapad <dpapad@chromium.org> Date: Wed Jun 14 18:51:04 2017 MD Settings: settings-subpage-search, add text ellipsis for placeholder text. BUG=733095 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation Review-Url: https://codereview.chromium.org/2940883005 Cr-Commit-Position: refs/heads/master@{#479456} [modify] https://crrev.com/0a9fd735b58bf6fe1a7eb2b9d743dc65650afc02/chrome/browser/resources/settings/settings_page/settings_subpage_search.html
,
Jun 14 2017
,
Jun 14 2017
,
Jun 15 2017
,
Jun 20 2017
Verified this issue using latest chrome version #61.0.3135.4 on Mac 10.12.4, Win 10 and Ubuntu 14.04 as well. Observed no chopping is seen after changing browser language. Please find the screen cast. Thanks!!
,
Jun 20 2017
,
Jun 6 2018
This seems to be happening again even though the code that fixed it the first time is still in place. Maybe something in blink changed - should bisect to find regression. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by nutan.ga...@etouch.net
, Jun 14 2017