|
|
Posted by dorayme on 03/13/06 00:01
In article <Xns978488B34C85Earbpenyahoocom@69.28.186.121>,
Adrienne Boswell <arbpen2003@sbcglobal.net> wrote:
> CSS itself is case sensitive, so #MyHeader and <h1 id="myheader"> are not
> the same. I found the out the hard way. Another one of the reasons I don't
> like mixed case.
Well, I think it is more true to say "CSS itself" is case
insensitive. There are special issues surrounding ids and classes
re their interpretation by browsers and the html (which has case
sensitivities). I still wonder about your use of "verdana"? It
looks wrong to me.
Generally I find it helpful to use case for readability, as in
#featuresColumn { etc in the CSS and id="featuresColumn" in the
html. But just be very consistent in this across in the html.
Yes, I realise you like to avoid the need by using all lower...
In the above name, #featuresColumn and #featurescolumn would be
quite the same as far as the CSS is concerned:
eg. one could have #featuresColumn p {color:red} and later in the
CSS sheet (or in a supplementary sheet), #featurescolumn p
{color:blue}
As far as the css is saying, all p paras in the id that is spelt
f e a t u r e s c o l u m n should be blue.
Browsers will react differently according to how they read the
standards, since ids and classes are mentioned in both css and
html, the former being case insensitive the latter sometimes at
least being case sensitive, there is somewhat a conflict of
interest.
--
dorayme
Navigation:
[Reply to this message]
|