Thierry Koblentz

@jhthorsen what would be the advantage of using `overflow-x:auto` instead of `overflow:auto`?

I think we already have the "[clip technique](https://developer.yahoo.com/blogs/ydn/clip-hidden-content-better-accessibility-53456.html)" for this. To me, the problem is not how we can visually hide content but rather how to deal with focusable elements...

@Ian-Y this approach works for focusable elements (i.e. skip links) but it does not work on hidden elements that *contain* focusable elements.

As @jnurthen suggested, this seems related to JS as the markup looks fine. In any case, I think `aria-label` to convey/fake "link text" to screen-readers is a better choice than...

I don't think `vertical-align:top` plays a role in this rule that includes `float:left`: ```css .warning-title:before { content: "⚠"; /*U+26A0 WARNING SIGN*/ font-size: 3em; float: left; height: 100%; padding-right: .3em; vertical-align:...

We did discuss the value of shorthand versus longhand and agreed that using the latter was better from a performance/optimization perspective (class re-use). I do think there is value in...

`Bgp()` now allows the passing of multiple values via comma but I don't really like that as it departs from ACSS efforts to use the same characters as in "plain...

> neither works in https://pankajparashar-zz.github.io/atomizer-web/ ... Hi @xialvjun, Please note that @pankajparashar-zz's tool uses Atomizer **v3.2.1**: ``` /** * Generated using Atomizer build v3.2.1. * Copyright (c) 2015, Yahoo Inc....

Sorry @xialvjun, I read the comment above ("for box-shadows this 'crazy' syntax can work") from @idmytro and assume that there had been a PR for this, but I've checked the...

Makes sense to me