Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Issue 103175 Font issue on a specific site - regression in chrome 17
Starred by 0 users Reported by fabios4r...@gmail.com, Nov 6 2011 Back to list
Status: Archived
Owner:
Closed: Aug 2015
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment
Chrome Version       : 17.0.929.0
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) : http://www.windowsette.com/

What steps will reproduce the problem?
1. navigate to http://www.windowsette.com/
2. compare the titles output with chrome v16 or firefox / IE
3.

What is the expected result?
titles are nice as in other browsers

What happens instead?
titles are really bigger and uglier

Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/535.8 (KHTML, like Gecko) Chrome/17.0.929.0 Safari/535.8


 
Comment 1 by tkent@chromium.org, Nov 7 2011
Labels: -Area-Undefined Area-WebKit WebKit-Fonts
Woud you provide a screenshot please?

Comment 2 by kareng@google.com, Nov 7 2011
Labels: Action-FeedbackNeeded
Owner: keishi@chromium.org
Status: Assigned
screenshots
chrome v15 ok.jpg
182 KB View Download
chrome v17 ko .jpg
189 KB View Download
Can you triage this issue? I provided screenshots and the issue is still reproducible in 17.0.937.0 tks
this is now fixed somehow
Project Member Comment 6 by bugdroid1@chromium.org, Mar 9 2013
Labels: -Action-FeedbackNeeded Needs-Feedback
Project Member Comment 7 by bugdroid1@chromium.org, Mar 10 2013
Labels: -Area-WebKit -WebKit-Fonts Cr-Content Cr-Content-Fonts
Project Member Comment 8 by bugdroid1@chromium.org, Apr 6 2013
Labels: -Cr-Content Cr-Blink
Project Member Comment 9 by bugdroid1@chromium.org, Apr 6 2013
Labels: -Cr-Content-Fonts Cr-Blink-Fonts
Status: Archived
(Automated-archive) Issue requiring feedback hasn't been modified/ commented on in more than one year, please file a new bug if this is still an issue.
Sign in to add a comment