Created attachment 190254 [details]
Create a page with the following contents:
<div style="white-space:nowrap;float:left;outline:1px solid red">
<!-- Fix 2: remove float:left (WAT!) -->
<!-- Remove width:100% to trigger the issue in Chrome 24 as well -->
<div style="width:400px;outline: 1px solid blue">
Cell 2, with a 400px DIV.
The red DIV has been forced to be 200px wide but it has a 400 px (blue) DIV inside of it. Therefore, "Cell 1" should shrink to its very minimum, but it is matching the sice of "Cell 2".
Check the comments for two possible "fixes" :/
This issue impacts CKEditor dialogs rendering:
Confirmed with Chrome 25.0.1364.99 and Safari 6.0.2 (8536.26.17). Works well with Chrome 24.
Although we've noticed the issue in Chrome 25, if you follow the source code comments and remove that width:100%, the same issue can be confirmed with Chrome 24 as well.
I don't see any difference between Safari 6.0.2, current ToT, and Chrome 25 on this test case.
Created attachment 190677 [details]
TC Screenshot with Chrome 24 = GOOD
Created attachment 190678 [details]
TC Screenshot with Chrome 25/26 = BAD
(In reply to comment #2)
> I don't see any difference between Safari 6.0.2, current ToT, and Chrome 25 on this test case.
The difference is not between Safari and Chrome. As described in my original message, I've confirmed the issue in both browser. Sorry if I didn't make it clear.
The difference can be seen with Chrome 25/26 and Chrome 24. The TC works well with the older version, but not with newer ones. I'm sure the same may happen with older Safari versions, but that's not the point. The point is that it works well with WebKit 537.17 (Chrome 24) but got broken at some point after that, confirmed with WebKit 537.22 (Chrome 25).
I have attached a screenshot made with Chrome 24 and Chrome 25 that shows the difference.
Sorry for the "retina sized" screenshots :)
Created attachment 191380 [details]
smaller test case
Here's a simplified testcase. I didn't verify if this was a regression, but I did verify that Chrome 26 does not match IE9 or FF19. So, I think we can call this a legitimate bug.
I bisected the original test case to r133037.
Ojan's test case appears to fail on all versions of Chrome that I tested (back to Chrome 18). I think it's also a bug, but not exactly the same as the original test case.
(In reply to comment #8)
> I bisected the original test case to r133037.
> Ojan's test case appears to fail on all versions of Chrome that I tested (back to Chrome 18). I think it's also a bug, but not exactly the same as the original test case.
This issue is indeed a regression caused by r133037. I would readily work on this but currently i am travelling, till the 18th of march, and can only work on this issue post 18th.
If required, please feel free to revert my change else after 18th I will definitely work on a fix for the same.
Apologize for the inconvenience and the delay.
Arpita: are you looking at this regression?
(In reply to comment #10)
> Arpita: are you looking at this regression?
Hi Robert, as a matter of fact fixing this regression had always been at the top of my agenda, but it kept getting sidelined due to some other priorities at work.
However, I definitely intend to make some time for it now! Thanks for bringing this back to my attention. :)
Created attachment 202816 [details]
Created attachment 202958 [details]
Comment on attachment 202958 [details]
The patch doesn't apply against the current state of WebKit. Could you please provide an up-to-date patch for review?