On 10/26/13, 8:01 AM, Colin (Sandy) Pittendrigh wrote:
[...]
Or is there a current benefit--that's worth the effort--of using the new
stuff now?
[...]
As a non-expert myself, I'm struggling with the same conflicts.
So far, I have found flaws in most current methods of laying out pages. Float
26 oct 2013 17.01 Colin (Sandy) Pittendrigh:
> Or is there a current benefit--that's worth the effort--of using the new
> stuff now?
Always embrace the latest browsers and work with that, simply giving older
browsers another experience. You can also use poly-fils to some extent while
the older
I did some searching. A combination of flexbox layout and srcset images
may (eventually) make responsive design a non-issue. But in the meantime
there are browser version and prefixing issues to learn first, before
attempting to use any of it. All of this looks promising (I'm a beginner,
not an
Thanks for the reply/answer/code Philippe! It's much appreciated.
On Fri, Oct 25, 2013 at 11:01 PM, Philippe Wittenbergh wrote:
> Directly? I don’t think so - all those (:first-*, :last-*) pseudo-classes
> target real elements in the DOM.
Ah, that's good to know. Thanks for the clarification. :
Le 26 oct. 2013 à 14:42, Micky Hulse a écrit :
> When using a flexbox layout, and re-ordering columns (for example)
> using the "order" property, is there a way to target the "visible"
> first/last child?
>
> Everything I try only affects the actual ordering of elements in the
> source code, no
When using a flexbox layout, and re-ordering columns (for example)
using the "order" property, is there a way to target the "visible"
first/last child?
Everything I try only affects the actual ordering of elements in the
source code, not the ordering that's set via "order".
Thanks!
__
