gt; given this example:
>
> [class*="span"]
>
> This means "select elements who's class contains the word 'span'". Correct?
>
>
>
> On Thu, Aug 14, 2014 at 9:39 AM, Frank Taylor
> wrote:
>> Yes, that’s correct. It’s the attribute se
Yes, that’s correct. It’s the attribute selector. Whatever goes into the
brackets is an attribute, and that can be any attribute on the HTML selector.
Shameless self-plug: there’s some crazy stuff you can do with the attribute
selector:
http://blog.frankmtaylor.com/2012/04/27/css-sorcery-perfo
8 août 2014 à 21:55, Frank Taylor a écrit :
>
>> flex-wrap doesn’t work in FireFox. **still**. It’s best to assume that
>> everything is flex-wrap: nowrap for a good while; at last reading, they had
>> no immediate plans to solve this.
>
> uh ?
>
> fl
8 août 2014 à 21:55, Frank Taylor a écrit :
>
>> flex-wrap doesn’t work in FireFox. **still**. It’s best to assume that
>> everything is flex-wrap: nowrap for a good while; at last reading, they had
>> no immediate plans to solve this.
>
> uh ?
>
> fl
accept the unprefixed
syntax, Safari and Opera will not.
Forms are tricky. seems to refuse to accept ‘display:flex’, no
matter how much that I insist that it should. Same with , and
On Aug 8, 2014, at 14:49, Tim Dawson wrote:
> On 08/08/2014 13:32, Frank Taylor wrote:
>> I’m unfami
I’m unfamiliar with the Compass syntax. However, the syntax looks old.
First get the wrapper in order:
start with “display:flex” for the parent container. then “flex-direction: row”
to set the orientation of the child elements. Then justify-content.
justify-content will set the position of yo
Howdy all,
I’ve noticed this for a while, but it’s starting to drive me nuts. It seems
like Flexbox properties don’t work on the element in Chrome or
FireFox.
Is there a reason for this? Are form elements not supposed to use the flex box
module?
here’s a quick example:
http://www.cssdesk.
Howdy all,
I’ve noticed this for a while, but it’s starting to drive me nuts. It seems
like Flexbox properties don’t work on the element in Chrome or
FireFox.
Is there a reason for this? Are form elements not supposed to use the flex box
module?
here’s a quick example:
http://www.cssdesk.
Hi All,
I apologize in advance for an off-topic question.
I’ve been following this group for a while now and have learned a ton from it.
Are there any groups like this one, but for HTML or JavaScript?
__
css-discuss [css-d@
Your one and only caveat is IE7: if there are HTML comments between the divs,
then the adjacent sibling selector doesn't work.
In the one case where our CMS was kicking out comments, I reverted to the
non-adjacent selector:
>> .wrap div ~ div ~ div {margin-right:0;}
Mind you, if you're deal
rap div + div + div {margin-right:0;}
>
>
>
>
>
>
>
On Jun 12, 2013, at 2:46 PM, Tom Livingston wrote:
> On Wed, Jun 12, 2013 at 4:31 PM, Frank Taylor
> wrote:
>> So far I've only had to really use the :nth-type selectors for tables, a
So far I've only had to really use the :nth-type selectors for tables, and for
creating some demos on layouts.
When it comes to tables, I'd created an html table-maker that optionally
generates helper classes.
Outside of tables, I really haven't had projects that required :nth-child
support
AM, Philippe Wittenbergh wrote:
>
> Le 22 oct. 2012 à 15:50, Frank Taylor a écrit :
>
>> I'm working on an application where the client wants input[type="textbox"]
>> to look more like a sliding on/off switch than a typical checkbox. I was
>> able to
Hi Guys,
I'm working on an application where the client wants input[type="textbox"] to
look more like a sliding on/off switch than a typical checkbox. I was able to
produce the desired effect for -webkit browsers: http://cssdesk.com/jJd87
But, It would appear as though :after{content:"blah"}
14 matches
Mail list logo
