On Nov 8, 2013, at 5:12 PM, MiB wrote:
>
> 8 nov 2013 23.47 John D:
>
>> What is the advantage of using an ID here?
>
>
> Identifying a particular page on the site. This can be used for instance in
> descending selectors for the navigation:
>
> body#about-us-page nav li#about-us {
> /*Apply
8 nov 2013 23.47 John D:
> What is the advantage of using an ID here?
Identifying a particular page on the site. This can be used for instance in
descending selectors for the navigation:
body#about-us-page nav li#about-us {
/*Apply styles for current page*/
}
//and with class for a select
> Since
> there is (by definition) exactly one element, and since it
> is highly unlikely that any other element should be styled
> identically to the element (in all aspects, that is,
> not just in some aspects such as the choice of font-family),
> then I would have thought that an ID was to
8 nov 2013 12.08 Karl DeSaulniers:
> I just Id the container div and go from there.
Well, I guess the more we are moving away from the page concept as such towards
marked up self-containing and context-adapting "packages" that could turn up in
several places, then any page construct identified
On Nov 8, 2013, at 4:30 AM, MiB wrote:
>
> 8 nov 2013 03.09 Karl DeSaulniers:
>
>>
>> Ah I see. Well normally you wouldn't put an ID on the body anyways, you
>> would put a class wouldn't you? That is if your trying to style it.
>
> What's the logic behind choosing a class attribute here? Is
8 nov 2013 03.09 Karl DeSaulniers:
>
> Ah I see. Well normally you wouldn't put an ID on the body anyways, you would
> put a class wouldn't you? That is if your trying to style it.
What's the logic behind choosing a class attribute here? Is it mostly for
semantic reasons? Semantically I can s
> On Nov 8, 2013, at 1:56 AM, Philip TAYLOR wrote:
>
>
>
> Karl DeSaulniers wrote:
>
>> Ah I see. Well normally you wouldn't put an ID on the body anyways, you
>> would put a class wouldn't you? That is if your trying to style it.
>
> Personally I would not (recommend a class in preference