Re: [css-d] Universal selector vs. body selector

2009-10-07 Thread Ezequiel Garzón
Thank you, Philippe! It's interesting that the anchor's color doesn't seem to be specified in the W3C document. __ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://

Re: [css-d] Universal selector vs. body selector

2009-10-06 Thread Philippe Wittenbergh
On Oct 7, 2009, at 4:28 AM, Ezequiel Garzón wrote: > Thank you all for your replies! They have taught me a lot in very > little > time. > > Is it possible to open the default stylesheet? Are settings such as > 'a { > color: blue; text-decoration: underline; }' de facto or formal > standard

Re: [css-d] Universal selector vs. body selector

2009-10-06 Thread Ezequiel Garzón
Thank you all for your replies! They have taught me a lot in very little time. Is it possible to open the default stylesheet? Are settings such as 'a { color: blue; text-decoration: underline; }' de facto or formal standards? Cheers, Ezequiel

Re: [css-d] Universal selector vs. body selector

2009-10-06 Thread Bobby Jack
--- On Tue, 10/6/09, Ezequiel Garzón wrote: > Greetings. As you will be able to > tell, I'm a CSS rookie. My doubt is, > if the body contains all the other containers, why does > body { ... } > behave different from * { ... }? Aren't properties supposed > to > cascade? Inheritable properties at l

Re: [css-d] Universal selector vs. body selector

2009-10-06 Thread Climis, Tim
Greetings. As you will be able to tell, I'm a CSS rookie. My doubt is, if the body contains all the other containers, why does body { ... } behave different from * { ... }? Aren't properties supposed to cascade? Inheritable properties at least, no? But then I find that body { color:black; } and

Re: [css-d] Universal selector vs. body selector

2009-10-06 Thread Philippe Wittenbergh
On Oct 6, 2009, at 9:47 PM, Ezequiel Garzón wrote: > My doubt is, > if the body contains all the other containers, why does body { ... } > behave different from * { ... }? Aren't properties supposed to > cascade? Inheritable properties at least, no? But then I find that > > body { color:black; }

[css-d] Universal selector vs. body selector

2009-10-06 Thread Ezequiel Garzón
Greetings. As you will be able to tell, I'm a CSS rookie. My doubt is, if the body contains all the other containers, why does body { ... } behave different from * { ... }? Aren't properties supposed to cascade? Inheritable properties at least, no? But then I find that body { color:black; } and

Re: [css-d] universal selector to set defaults

2007-01-31 Thread James Leslie
; } img{ border:0: } Hope that helps, James -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Garth Jantzen Sent: 31 January 2007 02:37 To: css-d@lists.css-discuss.org Subject: [css-d] universal selector to set defaults real quick, i want to use the

Re: [css-d] universal selector to set defaults

2007-01-30 Thread George Ornbo
On 1/31/07, Garth Jantzen <[EMAIL PROTECTED]> wrote: > > real quick, > > i want to use the * selector to set all my default values (except fonts, i > know they will cascade). something like this: > > > * { > margin: 0; > padding: 0; > list-style: none; > font-style:

[css-d] universal selector to set defaults

2007-01-30 Thread Garth Jantzen
real quick, i want to use the * selector to set all my default values (except fonts, i know they will cascade). something like this: * { margin: 0; padding: 0; list-style: none; font-style: normal; font-weight: normal; border-collapse: collapse;

Re: [css-d] universal selector horror

2006-10-17 Thread Bjoern Hoehrmann
* Raymond Rodriguez wrote: >It's supposed to look like this in the end but I've not been >successful in my attempt at assigning selectors to the body. There is >a container on the right-hand side that I named "#infoSidebar" (line >73 in the CSS file) and I attempted to assign it universally t

[css-d] universal selector horror

2006-10-17 Thread Raymond Rodriguez
Hello again. I'm doing some reorganization of my CSS for this page. I'm focusing on getting only this page to look right and then I'll reassign the other pages to the new CSS file. It's supposed to look like this in the end but I've not been successful in my attempt at assigning selectors to

Re: [css-d] Universal selector

2006-10-12 Thread Kenny Graham
Gunlaug Sørtun wrote: > Use of the universal selector > makes no other sense than that it adds specificity to the plain > ID-selector. Rimantas Liubertas wrote: > The first rule will apply to the element with the id="leftcol" > regardless of it's position in DOM. The universal selector in the fir

Re: [css-d] Universal selector

2006-10-12 Thread Mark J. Reed
On 10/10/06, Jørgen Farum Jensen <[EMAIL PROTECTED]> wrote: > Is there any difference at all between > * #leftcol {font-family:arial,sans-serif;} > #leftcol * {font-family:arial,sans-serif;} The first one is equivalent to this version, with no * at all: #leftcol {font-family: arial, sans-serif;

Re: [css-d] Universal selector

2006-10-12 Thread Gunlaug Sørtun
Jørgen Farum Jensen wrote: > Is there any difference at all between > * #leftcol {font-family:arial,sans-serif;} > and > #leftcol * {font-family:arial,sans-serif;} Definitely! The first example targets #leftcol _inside_ _any_ element, but *only* #leftcol (and elements inside #leftcol). Use of

Re: [css-d] Universal selector

2006-10-12 Thread Rimantas Liubertas
> Is there any difference at all between > * #leftcol {font-family:arial,sans-serif;} > and > #leftcol * {font-family:arial,sans-serif;} Yes, there is. The first rule will apply to the element with the id="leftcol" regardless of it's position in DOM. The second rule will apply to _all elements_ w

[css-d] Universal selector

2006-10-12 Thread Jørgen Farum Jensen
Is there any difference at all between * #leftcol {font-family:arial,sans-serif;} and #leftcol * {font-family:arial,sans-serif;} -- Med venlig hilsen Jørgen Farum Jensen http://www.webdesign101.dk __ css-discuss [EMAIL PROTECTE