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

Issue 139502 link

Starred by 7 users

Issue metadata

Status: Fixed
Closed: Sep 2012
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression

Blocked on:
issue 140345

Sign in to add a comment

REGRESSION: Rendering difference in Chrome 21 and 22 that affected on Persian Wikipedia

Reported by, Jul 28 2012

Issue description

Chrome Version       : 22.0.1219.0
OS Version: 6.2 (Windows 8)
URLs (if applicable) : or simplified attached test-case
Other browsers tested:
  Chrome < 22: OK
    Chrome 22: FAIL
       Others: OK

What steps will reproduce the problem?
Open linked URL or test-case on Chrome 21 and Chrome 22

What is the expected result?
They must be same.

What happens instead?
But they are not.

Please provide any additional information below. Attach a screenshot if

UserAgentString: Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.3 (KHTML, like Gecko) Chrome/22.0.1219.0 Safari/537.3

Increasing font-size is interesting here, this bug is available on font-size: 110%; and font-size: 111%; but it will disappeared on font-size: 112%;!!! (please increase it on web inspector with up-down arrow keys)

287 bytes View Download
45.2 KB View Download

Comment 1 by, Jul 30 2012

Labels: WebKit-Fonts

Comment 2 by, Jul 30 2012

Also here is another interesting bug that occurred on Chrome 21 also (but was not available on older versions) on this, look for "Malaysian sport stubs" and compare it with Firefox, IE, Opera and ...
193 KB View Download

Comment 3 by, Jul 30 2012

Labels: -Type-Bug -Pri-2 -Area-Undefined Type-Regression Pri-1 Area-WebKit WebKit-Rendering Action-BisectNeeded
Status: Untriaged
Summary: REGRESSION: Rendering difference in Chrome 21 and 22 that affected on Persian Wikipedia
For , just changing webpage zoom from the UI will reproduce the problem.

Comment 4 by, Jul 30 2012

Just a little comment, I have this on any zoom level lower than 125% (and default zoom)
In the attachment, the other bug on Wikipedia and my screen DPI and resoulation is available.
565 KB View Download

Comment 5 by, Jul 30 2012

Status: Started

Comment 6 by, Jul 30 2012

Labels: Mstone-22
Minimal test case. Triggered by a combination of border and padding at certain font sizes.
653 bytes View Download

Comment 7 by, Jul 31 2012

Upstream WebKit bug:

Comment 8 by, Jul 31 2012

 Issue 135566  has been merged into this issue.
Thanks for fixing this bug! :)
Please add this on your test-cases:

Another screenshot
231 KB View Download

Comment 11 by, Aug 1 2012

 Issue 140035  has been merged into this issue.

Comment 12 by, Aug 1 2012

 Issue 140038  has been merged into this issue.

Comment 13 by, Aug 1 2012

Status: Fixed
Committed: <>

Comment 14 by, Aug 2 2012

Labels: -Mstone-22 Mstone-21 Merge-Requested

Comment 15 by, Aug 2 2012

Status: Started

Comment 16 by, Aug 2 2012

Labels: -Merge-Requested Merge-Approved

Comment 17 by, Aug 2 2012

This change depends on WebKit r90083 which is not in M21. Holding off merging for now.

Comment 18 by, Aug 2 2012

Blockedon: chromium:140345

Comment 19 by, Aug 2 2012

Labels: -Action-BisectNeeded -Merge-Approved Merge-Merged
Status: Fixed
On the last Chrome Canary, the bug that pointed on #c2 is fixed but the first bug and #c10 is not fixed. This bug is not fixed
Yes, c#0 and c#10 problems are not fixed on Canary 22.0.1225.0 (tried on Win7).

@eae, are they supposed to be fixed or which Chrome versions will have the mentioned WebKit fixes?
@kareng:  Issue 140035  is fixed but  Issue 140038  is not fixed on last Canary.
Tested the same on 21.0.1180.74 in Win7, MAC 10.7.4 and Linux 10.4. It is working fine(C0,C2 and C10), please find that attached screenshots.

Due to lack of Windows 8 machine, I am unable to test on Windows 8 environment.
449 KB View Download
318 KB View Download
531 KB View Download
@rponnada: Thanks for testing but sorry, but can you please test them on Chrome 22 (dev or canary version)? It is a rendering difference between Chrome 21 and Chrome 22 (c2 was a shared bug between them). I don't think this is a Windows 8 specific bug as you can see @krtulmay had not Windows 8.
Tested in Chrome 21.0.1180.75 and 22.0.1229.0 canary on Windows 7

Bug in comment#2 is fixed

First bug and comment#10 bug is not fixed
Reopening as per latest comments.
Aditya.. Pls verify this once it is fixed.
Labels: Action-BisectNeeded
Aditya . Could u please run the bisect tool and provide the regression range for comment #10
Labels: -Action-BisectNeeded
Regression Range for comment#10:

You are probably looking for a change made after 145646 (known good), but no later than 145652 (first known bad).
That WebKit range doesn't appear to include any layout changes... that seems unlikely.
From manual bisect:

Good build: 22.0.1201.0
Bad build: 22.0.1202.0

corresponding CL:

Comment 32 by, Aug 8 2012

Owner: ----
Status: Untriaged
Labels: -Mstone-21 -Merge-Merged Mstone-22 Merge-Merged-1180
inferno@: could you please triage it based on comment #31.
Owner: ----
I have no idea what bug we are talking about here. can anyone provide a reduced testcase so that we can see what regressed here.
For first bug: (comment#0)

I believe this test-case is simple enough to show the problem:
data:text/html;charset=utf-8,<style>li { margin-left: 0.75em; float: right; } ul { position: absolute; font-size: 110%; }</style><ul><li>a</li><li>b</li><li>c</li></ul>
(comparing screenshot is attached)

If it is not simple enough, ping me again and I will try to make a simpler one :)

I think this rendering is important enough to be solved because Persian Wikipedia UI will affected from this.

55.9 KB View Download
I think for making things clearer, I want to propose that you can un-merge  Issue 135566  and merge  Issue 140035  into it and mark that bug as FIXED. That bug is fixed on #c13 and it was the bug that I said on #c2. Thanks for fixing that :)

Also  Issue 140038  seems unrelated to this bug and it can un-merged also.

Sorry for making things complicated
data:text/html;charset=utf-8,<head><style>li { margin-left: 0.75em; float: right; } ul { position: absolute; }</style></head><body onload="var i = 50; setInterval(function () { document.getElementsByTagName('ul')[0].style.fontSize = i + '%'; i++; if (i > 200) i = 50; }, 100);"><ul><li>a</li><li>b</li><li>c</li></ul></body>
A simple animation for showing this bug! :) (please test it on Chrome 22, it is okay on Chrome 21)
Here is another test-case show the bug that is pointed on c#10:
data:text/html;charset=utf-8,<table style="text-align:left; font-size: 110%;"><td><span style="float: right; margin-left: 0.5em;">b</span>a%20<span>c</span></td></table>
Re #37, I see wrapping at a couple font sizes on this build:

Google Chrome	22.0.1229.0 (Official Build 150285) dev
OS	Linux
WebKit	537.4 (@124835)
Sorry, I don't know what is mean of "I see wrapping at a couple font sizes". Because of this I uploaded a video of thing that I see by #37 on attachment of this comment (with 23.0.1231.0 canary). The normal behavior that I expect is Chrome 21 (21.0.1180.64 m), Firefox and Safari 5.1.7 behavior. If this is not happened there, please tell me and I will not care about this bug anymore :)
254 KB View Download
Labels: nomedia
As in comment 36, can anyone confirm that  Issue 140038  is a separate problem to what is being discussed here?
 Issue 140038  is a separate issue.  That one is about text wiggling when animated.

This bug is about line layout being broken, in that elements that are supposed to fit in their parent container sometimes wrap.

Comment 44 by, Aug 24 2012

is this issue fixed? we can open a new bug for the other issue. I believe the persian wikipedia issue is now gone or is it still there in m22?
I can agree! :)

In Chrome 23.0.1243.2 m (last dev version) it is fixed but on previous Chrome that I had (22.0.1229.12) was available. Thanks for fixing the main bug however comment#9 bug is not fixed yet (that occurred in English Wikipedia). Please make another bug for it if needed.

Thanks :)
Status: Fixed
Closing this bug as the original one is Fixed per comment #19.

Having several issues tracked by the same bug is confusing and has led to a state where only one bug was fixed and all the other ones felt between the cracks.

@ebrahim, if you still see some of the bugs mentioned here, open a new issue for each one and link them here. Commenting that seemingly unrelated bugs are not fixed here will only add to the confusion. Thanks!
Okay :) 
Project Member

Comment 48 by, Mar 9 2013

Labels: -Type-Regression -Area-WebKit -WebKit-Rendering -WebKit-Fonts -Mstone-22 Cr-Content Type-Bug-Regression Cr-Content-Fonts M-22 Cr-Content-Rendering
Project Member

Comment 49 by, Apr 6 2013

Labels: -Cr-Content Cr-Blink
Project Member

Comment 50 by, Apr 6 2013

Labels: -Cr-Content-Rendering Cr-Blink-Rendering
Project Member

Comment 51 by, Apr 6 2013

Labels: -Cr-Content-Fonts Cr-Blink-Fonts
Labels: -Cr-Blink-Rendering Cr-Blink-Layout
Migrate from Cr-Blink-Rendering to Cr-Blink-Layout

Sign in to add a comment