Closed tomalec closed 9 years ago
For the first look, it seems to be Chrome CSS Grid renderer bug, as CSS properties and HTML structure are exactly the same on page load as after re-pack, but the look differs.
Here's how it looks in Canary:
Is that what you would expect?
Yes, that's what is expected
So it seems to be fixed in Chrome Canary 46 (tested on Mac) and Chrome Beta 45 (tested on Win)
Are Playground apps affected?
If we are not using group properties like, text content, backgrounds, and borders we should not notice this.
Even if we use it may not necessarily pops up.
Chrome Version 44.0.2403.155 m
:
After page load:
After window resize:
Chrome canary on page load:
If we are not using group properties like, text content, backgrounds, and borders we should not notice this.
@miyconst are we using any of these, and if yes then can you check if they are broken?
I think it won't affect the apps we are going to present, but I will double check the People app, as it has the most complex layout.
Great, then I am NOT marking this as a requirement for the Playground. Let's leave this to be resolved by Chrome update. @miyconst please update this issue if you find this is actually a problem for our apps.
Btw. Chrome 45 (which is supposed to fix it, according to our investigation) should be released within less than few weeks.
See http://juicy.github.io/juicy-tile-grid/examples/oversize.html it seems that https://github.com/Juicy/juicy-tile-grid/commit/67385b4814b330d2304bf65f4a3187bde8122bb0 introduced new bug