We were using cookieless domains at quizlet.com for our static assets (css, js, images) for awhile, but recently turned them off. Some of our users (enough to b

We were using cookieless domains at quizlet.com for our static assets (css, js, images) for awhile, but recently turned them off. Some of our users (enough to be of concern) wrote in saying the site looked all wrong, and on closer inspection, weren't receiving our assets. Because we're used in a lot of school systems, and many school districts have weird rules (domain whitelists), our static domains were not resolving while our main quizlet.com was. We decided (for now) it wasn't worth investigating how many of our users were affected or if we could do a workaround. We're still using a subdomain off our main domain (a.quizlet.com) which prevents most cookies from sending but not al. Going forward, I'd prefer to start base64-embedding images in css (only for compliant browsers) and using more sprites to reduce the number of overall requests.