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

Issue 750598 link

Starred by 1 user
Status: Assigned
Owner:
malaykeshav@chromium.org
Cc:
ajha@chromium.org
█ kavvaru@chromium.org
█ brajkumar@chromium.org
osh...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression


Show other hotlists

Hotlists containing this issue:
Fixing-touch


Sign in to add a comment

Regression:Weird color is seen for apostrophe in omnibox

Project Member Reported by rkalavakuntla@chromium.org, Jul 31 2017 
Chrome Version:62.0.369.0/9794.0.0 dev-channel Kip,Paine & Parrot.
OS:Chrome

What steps will reproduce the problem?
(1)Sign in to user ->Launch Chrome ->In Omnibox,enter apostrophe (''''''''''') and observe (please refer screenshot)

Actual:Weird color is seen for apostrophe
Expected:No such weird color should be seen

This is a Regression issue as same is working fine in 61.0.3163.16/9765.12.0 dev channel Kip

Note:Issue is not seen in Windows,Linux OS
Actual.jpg
5.1 MB View Download
Expected.jpg
7.3 MB View Download

Comment 1 by jdonnelly@chromium.org, Aug 1 2017

Components: Internals>Views
Labels: Needs-Feedback
Status: Available (was: Untriaged)
Does the apostrophe appear with the normal color when typed in a plain form field (try [1])?

[1] Google Payments test site: https://dump-truck.appspot.com/usecase-address_then_cc/address.html

Comment 2 by mpear...@chromium.org, Dec 12 2017

Labels: Needs-TestConfirmation
Can someone confirm this is still an issue?

Comment 3 by rkalavakuntla@chromium.org, Dec 13 2017

Labels: -Needs-TestConfirmation -Needs-Feedback
Able to reproduce the issue on latest 65.0.3287.0/10210.0.0 dev channel Paine in a plain form field [1] mentioned in comment #1, as well as in Omnibox also.

Please find the attached screenshot for reference..
Thanks!

Comment 4 by rkalavakuntla@chromium.org, Dec 13 2017

Plain form feild.jpg
4.5 MB View Download

Comment 5 by mpear...@chromium.org, Jan 22 2018

Components: -UI>Browser>Omnibox UI>Input>Text
Moving to TextFields bug queue, per comment #3.

Comment 6 by afakhry@chromium.org, Feb 20 2018

Owner: pkasting@chromium.org
Status: Assigned (was: Available)
please triage if it's still an issue.

Comment 7 by pkasting@chromium.org, Feb 20 2018

Owner: ----
Status: Untriaged (was: Assigned)
Not sure why this was assigned to me, I don't work on text input.

Comment 8 by ovanieva@chromium.org, Mar 6 2018

Owner: kpschoedel@chromium.org
Status: Assigned (was: Untriaged)
kpschoedel@ please triage

Comment 9 by kpschoedel@chromium.org, Mar 6 2018

Owner: ovanieva@chromium.org
Not sure why this was assigned to me, I don't even work on the Chrome team!

This isn't an input problem — the user typed apostrophes and got apostrophes. I would be a good person to ask if they typed apostrophes and got semicolons.

My guess would be subpixel rendering gone wrong, but I don't know where that happens.

Comment 10 by ovanieva@chromium.org, Mar 6 2018

Owner: malaykeshav@chromium.org
apologies - reassigning to malay for triage

Comment 11 by ovanieva@chromium.org, Mar 6 2018

Labels: -Pri-1 -M-62 Pri-2

Comment 12 by malaykeshav@chromium.org, Mar 6 2018

Cc: osh...@chromium.org

Comment 13 by osh...@chromium.org, Mar 9 2018 

This can be an issue related to subpixel hinting.

ovanieva@, can you ask someone in QA team in MTV to confirm this behavior, and bring the device to me?
►

Sign in to add a comment