On 9/7/06, Kevin Futter [EMAIL PROTECTED] wrote:
Ironically, I actually *do* use #topNav a lot, but I selected this name in
the context of top *level* nav, rather than top *positioned* nav. It never
occurred to me that this might be semantically ambiguous. I guess
#primaryNav becomes the better
Patrick H. Lauke wrote:
Maybe it's philosophical hairsplitting, but indent still describes
the visual effect you're trying to achieve, rather than being a name
describing either the function or a characteristic of the content
itself. IMHO first falls under that second category (it's an
L-J Lacey wrote:
--- Designer [EMAIL PROTECTED]
wrote:
So, would you criticise this as 'not best practice'?
I think the point is that if you decided to change the
left images to the right/top/bottom/etc it would no
longer be semantic, and would potentially be confusing
for you later on, or
I often find myself using 'functional' class names for a handful of
specific tasks, but often these are used in parallel with semantic class
names, for example:
div class=navBar noPrint
.noPrint has only one simple rule, which I know will never change.
Similarly I occasionally use .leftAlign
RE: img.left, img.right
Designer wrote:
1) It's clear what it's for (semantic?)
I do the same thing for embedded images and I would think that this is okay
and finding another way would be a challenge. But I'll take a stab at it
since I've been enlightened on this a bit.
img.posA {}
Mike at Green-Beast.com wrote:
That said, for my clients, using .left, .right, .center will be more
intuitive.
exactly!
;o)
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe:
Tony Crockford wrote:
Mike at Green-Beast.com wrote:
That said, for my clients, using .left, .right, .center will be more
intuitive.
exactly!
For some clients it's also easier to use table layouts and font tags...
P
--
Patrick H. Lauke
Mike at Green-Beast.com wrote:
a img, img.posA, img.posB, img.posC {
background-color : #fff;
border : 0;
}
img.posA {
float : left;
margin : 0 15px 5px 0;
}
img.posB {
float : right;
margin : 0 0 5px 15px;
}
img.posC {
Hello Group,
For about a week I had a draft started on my blog. In answering Designer's
question about p:first-line a can of worms was opened up. I'm grateful
because it showed me a side of a topic I hadn't really considered previously
and was I prepared to simply write about the subject of
On 6 Sep 2006, at 12:13, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
I often find myself using 'functional' class names for a handful of
specific tasks, but often these are used in parallel with semantic
class
names, for example:
div class=navBar noPrint
.noPrint has only one simple
Patrick H. Lauke wrote:
I'd go with something along those lines, yes, or even more generically
(if you foresee that at some point you may not want all images on the
same position, but differentiate them some other way - e.g. one has a
blue border, the other a red border, etc) having classnames
David Dixon wrote:
A few people have pointed out that they use the .leftNav etc because
they are more useful to their clients and I would agree that .leftNav is
far more obvious than .col1. However, those names are only useful until
the site needs a redesign/restructure (actually 3 months
David Dixon wrote:
A few people have pointed out that they use the .leftNav etc because
they are more useful to their clients and I would agree that .leftNav is
far more obvious than .col1. However, those names are only useful until
the site needs a redesign/restructure (actually 3 months later
Lea de Groot wrote:
There aren't many cases where there is a need to do this.
So, when the answer to 'what will this do on the page?' starts with 'all
these items will...' then they should have a classname that is meaningful.
When the answer is 'they all do this; but some of them have this
David Dixon wrote:
Nice little blog entry you have there Mike,
I like the honesty you've conveyed in your
opinions [...]
Thank you David :-)
[...] what is this .col1? what's in it? does it have
a particular purpose? [...]
I agree in that it's not very telling as to what
On 7/9/06 10:37 AM, Elliot Schoemaker [EMAIL PROTECTED] wrote:
David Dixon wrote:
A few people have pointed out that they use the .leftNav etc because
they are more useful to their clients and I would agree that .leftNav is
far more obvious than .col1. However, those names are only useful
Not sounding grumpy at all Patrick. Sounding sensible. Semantic class names
are good!
I've just revisted the work of a programmer who wouldn't listen to me about
this, and has called coding variables $sideSubmenu and $sideRefine, because
OF COURSE every client I deal with is always going to
My my, if only I had a penny for every time this topic of conversation
was brought up on the list :p
Patrick is correct however in the standards evangelist sense ;)
p.indent describes the action of the class (what in x months time, i
decided that i didnt want to indent it, but colour it blue
David Dixon wrote:
Patrick is correct however in the standards evangelist sense ;)
p.indent describes the action of the class (what in x months time, i
decided that i didnt want to indent it, but colour it blue instead).
On
the other hand, p.first describes the element itself
19 matches
Mail list logo
