Elijah,
Sorry for the slow response. I've been swamped with work and moving,
so maintaining open source software hasn't made the top of my list in
a while.
I do recognize the issue, and have known about it for some time. This
is not a flaw in Susy, but a common issue of sub-pixel rounding -
solved differently by all browsers and constantly changing. This is,
in fact, one of the very first challenges that I had to solve in
developing Susy - but for IE6 (which always rounds up, breaking the
grid entirely).
Susy is built entirely on a philosophy of flexible (responsive) web
design. It is a direct alternative to the more pixel-perfect,
inflexible grid systems that came before compass (e.g. blueprint,
960). If you need that type of control, you should use those grid
systems. I believe Susy is a better approach to the web, working with
the strengths of the medium (such as flexibility and user control),
rather than fighting them. And, with that philosophy in mind, I have
had absolutely no trouble building complex and detailed designs that
are flexible enough to withstand the browser differences. Susy is not
meant to solve all problems, it is meant to solve the problem of
building extremely flexible and responsive sites that should remain
future-proof. Browser-sniffing to nudge pixels here and there is
decidedly not that.
There is no pixel-perfect solution for this that is both reliable and
maintainable across browsers, and I don't plan to incorporate browser-
sniffing hacks into the core of Susy. Feel free to make your own edits
and use/distribute them as you will.
There are also plenty of CSS solutions that can be used with Susy to
eliminate extra spaces. I highly recommend the habit of leaving
columns flexible whenever possible. Using the overflow property to
trigger layout context (as used in OOCSS and others) can be quite
useful for this.
Happy coding.
-e
> [2]
http://elasticss.com/determination-of-algorithms-used-for-percentage-...
>
> -elijah