Closed blueset closed 10 years ago
That's odd.
I'm unable to reproduce in Chrome stable, or Chrome Canary.
(I know the bug is with dev channel, but I'm wondering why it's not present in stable/canary builds.)
For reference…
Perhaps they're messing with how Chrome handles -webkit-*
CSS prefixes (preparing to switch to Blink)?
Thanks for bringing this to my attention.
I'm just not sure if there's anything I can do about it, until the dust settles on their rendering engine overhaul.
Update:
So, I guess it was a (regression?) bug in Chrome dev channel.
According to this tweets…
Also here is the link to the Susy bug: https://github.com/ericam/susy/issues/181
As a fellow grid system developer I am keeping an eye on but not actively changing code due to changes in unstable builds of browsers, especially Chrome as they are overhauling their entire rendering engine. IMO it is their problem to solve, not ours. If it somehow creeps into a release then it’s going to be our problem to solve.
If we end up having to fork code for different versions of Chrome, that's it.
I'll just retire.
:)
Here is the issue on the chrome issue queue: https://code.google.com/p/chromium/issues/detail?id=237751
Looks like it was fixed as of yesterday.
Closing this issue, since it was fixed on the Chrome side. Woot.
Disordered rows
All above rows disorder with browser width range from 785px to 1240px.
Tested with
Chrome dev-channel 28.0.1500.11 Windows 8 in Official Demo pages Responsive LTR and Adopt.js LTR
Screen shots