Yea, there are plenty of iContact coupons out there. Spiffy chance to save cash on iContact now. I advise you to sign up for their emails so you can get notified of their most up-to-date online discount codes. They usually release them once a week or 2..
<table style="border-bottom: 1px black;"> for the enclosing table would work, too..
I took a look at your code, too. I'm not sure about your link CSS. Firstly, you have the order wrong. It's:.
A:link.
A:visited.
A:hover.
A:active.
Cascading styles, remember. *g* What's written first, gets dealt with first..
Also, the way you have it now, there is no differentiation between the links and the visited links. Even two different shades of blue would help..
Other than that, it looks good. Nicely done!.
Peg..
>>.
Cascading styles, remember. *g* What's written first, gets dealt with first..
<<.
I thought that it was:.
What's written last overrules all that came before it...
Yep, but Peg is talking about.
A:.
Info from this site:.
Http://www.metalusions.com/backstage/articles/5/.
( More:.
Http://www.w3.org/TR/REC-CSS1.
).
A part of CSS which is often confusing for beginners and experts alike is the order in which the a:pseudo classes should be written..
General information.
There are a number of pseudo classes in CSS that when used in a selector are only matched under certain conditions. The most common of these are used mainly with <a> elements, these are :link, :visited, :hover and :active..
All <a href="..." ...>...</a> elements start off as a:link and once they have been visited become a:visited. A link may also be selected by a:active, a:hover or both. Those links which have a pointing device over the top of their boxes will be selected by a:hover and those which are currently active through that pointing device's clicking mechanism or a keyboard command will match a:active..
The order.
A common problem is that designers don't understand the way a set of CSS rules are used when more than one selector applies to an element..
A:link {.
Color: red;.
Background-color: white;.
}.
A:hover {.
Color: blue;.
Background-color: white;.
}.
A:visited {.
Color: lime;.
Background-color: white;.
}.
In the above example, plain links will be red and plain visited links will be lime, as only one of the pseudo classes apply. In the case of an unvisited link being hovered, the link will change from red to blue. This is because both a:link and a:hover apply in that situation so first the color: red; is applied and then color: blue;. The problem occurs when a visited link is hovered. As the order in which the styles are specified is hover and then visited, color: blue; is applied first and then color: lime;. Therefore all visited links are lime no matter whether they are being hovered or not..
The solution.
These sorts of problems can usually be overcome by using the order :link, :visited, :hover, :active. However for some interesting effects other orders can be used and experimenting with this can be a useful exercise..
A:link {.
Color: red;.
Background-color: white;.
}.
A:visited {.
Color: lime;.
Background-color: white;.
}.
A:hover {.
Color: blue;.
Background-color: white;.
}.
A:active {.
Color: black;.
Background-color: white;.
}..
In a sense, Giz, both statements are true. However, as Peter pointed out, the only place that really shows up is in the links..
I mean, think about it. The browser doesn't start looking for information in the middle of a page, does it? The first thing it does is read the doctype, then what type of document it is, <html>, the <head> information - meta tags, scripts, etc, - and so on..
What gets written first, gets dealt with first. It doesn't necessarily override any following information. Computers and browsers process information far faster than we do. Look how long it takes the average page to load onto our screens. For a simple table on a page, it takes no time at all to load, but the computer may have already read something like:.
Okay, external style sheet says black text. Got it..
Ooops. <script> says table information is to be in blue. Got it..
Oh. <span> says this cell is red text. Okay. Got it..
Processed and showing..
And all that, plus the rest of the page's information in a split second. Just because we only see the end result, it doesn't mean that the information hasn't been processed by the browser and the computer..
At least, that's the way I look at it..
Peg..
Heh,.
Peg.
You really are understanding this stuff!.
Good post, and Peter too. Good summary and clarification...
<blush> Yeah, scary, ain't it? *g*.
Mind you, it's taken me long enough. My brother started trying to teach me programming back in... *lol* Well, let's put it this way, all programmes had to have line numbers in order to work..
But the more I stare at the stuff, and the more I listen to people like you, Giz, the more I understand. *g* I still can't tell what a page will look like just by looking at the HTML, but I'm getting better at it. Actually, I'm finding it easier to 'see' an HTML page done without using tables for layout than I do a page with a table layout. Once I get this iFrame stuff figured out, I'll be trying that kind of layout for my own site..
Having to explain things to other people also helps me understand..
Oh, and I owe you a huge thanks, Giz. You've mentioned the HTML and CSS standards a couple of times and I downloaded the pdf file and printed it out. If I have a couple of minutes during the day, I'll browse through the binder I have the pages in and 'learn something new'. Thanks for bringing it to my attention..
Peg..
Heh! No problem, and while trying to help people here to understand HTML and CSS a little better, and spending lots of time trying to answer their questions, I'm also asking my own questions about PHP, and trying to learn it myself..
Never stop learning...