I haven't been using Sass for a little while so my attention to this library has diminished. I am looking for at least one other person to help maintain it -- preferably an active user of it.

Does anybody want to join in?

There are thousands and thousands of web developers who leverage the Compass ecosystem of Sass extensions. I believe there are way more people who use Sass with Compass than Sass with Bower:

http://www.google.com/trends/explore?q=sass+compass%2C+sass+bower

So please release Scut as a Compass extension. This requires like 20 minutes of your time, but you'll have to keep it up to date.

Also, you should tag commits that get released with corresponding version numbers. See http://semver.org/ .

I've received a couple of complaints that the docs are crashing people's iOS browsers (both Safari and Chrome, both iPhone and iPad).

This is strange, considering how simple the site is.

It was happening earlier in development and I tried a few things (making sure HTML validated and removing unnecessary resources):

• https://github.com/davidtheclark/scut/commit/cdbaa9f81f85f6637f452c3f1346f35531e413e4
• https://github.com/davidtheclark/scut/commit/0bc2f1ef72027d214c9a840b1478b3dd81cc2381
• https://github.com/davidtheclark/scut/commit/69c9e86bbee148153c0052b55832dc1e098885bf

I thought it was fixed because I was no longer able to reproduce the crash. But others seem to be able to.

So if you are having this problem and are able to troubleshoot in any way, please help out!

Hi, I've been researching sticky footers lately and I wondered what you thought of this approach:

http://www.joshrcook.com/a-responsive-sticky-footer/

It's the best solution I've found to date - you don't need to know the height of the footer and it works in IE8+ and in everything else I've tried. I haven't found any issues with it yet, and wondered if it could be included in Scut as an alternative approach?

Happy to discuss / research more etc. and provide a PR if you think this is worth it.

Cheers

I'm finding that the "cells" of my table-based vertical centering solution don't have a common selector and I'd rather not have to put a "scut-inner" or similar class on them. By updating the scut-vcenter-td @mixin to take a variable number of selectors, we can support different selectors for the inner and use the tag/class that is already in the markup without needing to introduce a non-semantic class.

If no list is provided, it still falls back to the .scut-inner selector.

It would be nice to make this also compatible with the new upcoming sass eyeglass. https://github.com/sass-eyeglass/eyeglass#writing-an-eyeglass-module-with-sass-files

Throwing out a tiny mixin to possibly include, for resetting the styling of anchor tags.

I regularly need to reset styling for <a> tags at the class-level, like so:

.my-link-class {
    text-decoration: none;
    color: inherit;
}

I've made a tiny mix-in for it, inspired by scut-list-unstyled. I reach for both of these regularly.

Any interest? Would be quick for me to whip up.

What about this for your great collection:

/* merge with above css */
.parent-element-to-video {
    position: relative; /* or absolute or fixed */
}
video {
    position: absolute;
    left: 50%; /* % of surrounding element */
    top: 50%;
    transform: translate(-50%, -50%); /* % of current element */
}

source excample: http://stackoverflow.com/questions/10797632/simulate-background-sizecover-on-video-or-img

this is a great alternative for backgrond-size: cover; for any html elements like img, video, or just a div. works great cross all browsers since ie9+

if I use :

ul {
        @include scut-list-custom("\00bb", 1.3em, .5em);
}

and later on:

.pagination ul {
        @include scut-list-divided("\00B7", 0.2em);
}

it will not work, as ul has styles set, which should be reset by scut-list-divided to work / overwrite.

it is:

/* reset list styling set by @include scut-list-custom */
ul > li:before {
            position: static;
            width: auto;
            content: '';
}

So it turns out it mightn't have been overthrow.js at all.

I digged a little further into the crashing issue and I found that on desktop, when scrolling, the FPS were continuously maxing out at and above 60FPS (this would be 2x3 times on mobile). On resource-lacking devices this could potentially cause the browser to crash.

The primary cause was that both the .list and .main divs were both set to position: absolute which meant that the whole page was being repainted on scroll. I've reduced this a bit by doing the following:

• .list no longer uses position: absolute, now uses position: fixed.
• .list uses the translateZ hack to hoist it to the GPU for better FPS when scrolling
• .main no longer uses position: absolute, instead it is default position with padding-left: 16em.

If you do a before and after, measuring the frame rate on scroll you'll see it's a lot more respectable. You can read more about the background on this here

A few things to note.

• I haven't actually been able to test this on my mobile device as I'm having issues getting it to see my local environment. I've only tested it in the browser
• I wasn't sure what you're preferred way of doing auto-prefixing CSS was, so I just input all the possible css values.

Added another vertical-center mixin that archieves it with transform: translate.

It does not require any width or height which makes it ideal in some environments-

downside: It does not work in IE8 and below