Wrong Character
Reported by
guillerg...@gmail.com,
Nov 10 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 Example URL: Steps to reproduce the problem: 1. Open google.com 2. Search for character ฏ๎๎๎๎๎๎๎๎๎๎๎๎๎๎๎๎๎๎๎๎๎๎๎๎๎๎๎๎ or ค้้้้้้้้้้้้้้้้้้้้้้้้้้้้้. 3. What is the expected behavior? What went wrong? Some of the entries show a streak of weird characters floating upwards Does it occur on multiple sites: Yes Is it a problem with a plugin? N/A Did this work before? No Does this work in other browsers? No Mozilla Firefox Chrome version: <Copy from: 'about:version'> Channel: stable OS Version: Flash Version: Shockwave Flash 11.2 r202
,
Nov 12 2016
Issue tested on: Windows 10 1607 using Google Chrome ver (54.0.2840.99 m), Firefox 49.0.2 and Opera 41.0.2353.56. Ubuntu 16.04 using Firefox 49.0.2, Chromium ver 53.0.2785.143 All the same issue, also I searched it on Bing and Yahoo. But I found quite intereting with Yandex there is no issue (tested on Chrome and Firefox). Maybe the issue is in Google search engine's, also Bing and Yahoo ones. Thank for your attention.
,
Nov 12 2016
,
Nov 12 2016
#2, #3: yandex simply hides the bugs by using CSS property "overflow: hidden" ====== The character in question has several dozens of added diacritics, all rendered in Chrome and some other programs I've tried (like a harfbuzz/freetype-based Aegisub). I'm not an expert on this, so here's a link that suggests using Unicode normalization form C instead of form D: https://stackoverflow.com/questions/11978912/how-to-protect-against-diacritics-aka-unicode-combining-characters-zalgo
,
Nov 14 2016
The bug doesn't look to be Chrome related and probably specific to Google Search App. Labelling accordingly for more inputs on this from the respective team.
,
Nov 14 2016
,
Nov 16 2016
The characters are rendered as they're supposed to be and as intended by the content authors. Google search might want to clip the results, tracked in internal issue no 2512113. This is not a chrome bug as is working as intended.
,
Jun 4 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by sureshkumari@chromium.org
, Nov 11 2016Labels: Needs-Feedback