I show a error in Firebug the FF extension but I have no idea what it means or if it will help. Here it is.

missing ; before statement
all-spice.js (line 9)
<script type="text/javascript">

I have no idea either hehe. But when I visited your page the little error x said "befuddle 4evrblu." Do you use firefox. If you do get the extension snop mentioned firebug and it seems to have a JS debugger.

Debug and profile JavaScript

Firebug includes a powerful JavaScript debugger that lets you pause execution at any time and have look at the state of the world. If your code is a little sluggish, use the JavaScript profiler to measure performance and find bottlenecks fast.

I'll just get my own bakie.

I looked at the source of JavaScript manually and found the problem within 10 seconds...

function MM_preloadImages() { //v3.0
var d=document; if(d.images){ if(!d.MM_p) d.MM_p=new Array();
var i,j=d.MM_p.length,a=MM_preloadImages.arguments; for(i=0; i<a.length; i++)
if (a[i].indexOf("#")!=0){ d.MM_p[j]=new Image; d.MM_p[j++].src=a[i];}}
}

Find the above, see the second line, it's missing the closing ; at the end of the line. So replace the above code with:

function MM_preloadImages() { //v3.0
var d=document; if(d.images){ if(!d.MM_p) d.MM_p=new Array();
var i,j=d.MM_p.length,a=MM_preloadImages.arguments; for(i=0; i<a.length; i++);
if (a[i].indexOf("#")!=0){ d.MM_p[j]=new Image; d.MM_p[j++].src=a[i];}}
}

Then it will be fine. Simple as to be honest.

Posted By: DraiconeIt means there's an error in your Javascript code. After a quick glance I couldn't see anything wrong, but look for a semicolon at the end of every line. You can also use the Web Developer toolbar for Firefox to analyse these things, I find it's far more in depth and effective than Firebug.

Wow. That Web Developer is powerful. You definately get a cookie.

@Chris.....You too.... a cookie

And @icyone, I am even given you one. They are fresh baked, and I wish to thank you all.

Now, some of you may have noticed that the cookies look as though they have been licked, and the raisins picked out of them. Ummm.....just ignore that. Trust me, they are good.

Yes, I understand it's a valid error, I fixed it when I saw it, but it's not exactly the most descriptive

And in this instance the for loop does need the curly braces because it has to enclose successive statements involving more than one command. This code:
<code>for(i=0; i<a.length; i++);</code>
Is certainly, while probably valid, redundant and incorrect. If you omit the curly braces you have to have the actual statement immediately afterwards, as I'm sure you're familiar with. The semicolon terminates the command. If the d.MM_p[j++].src=a[i]; line didn't exist, though, it could all be shortened to for(i=0; i<a.length; i++) if(a[i].indexOf("#")!=0) d.MM_p[j]=new Image;.

Actually, forget all that. Here's the actual error in your code. You are including wordpress/wp-content/themes/fjords01-10/js/all-spice.js as a script file. However, if you include it as a script file, it has to include pure JavaScript. Sometimes browsers let you get away with one set of script tags in the .js file. The problem is when it encounters this:
//-->
</script>

<script type="text/javascript">
<!--
Now, this is the part of the actual page source where it includes the .js file:
<script language="javascript" type="text/javascript"
src="/wordpress/wp-content/themes/fjords01-10/js/all-spice.js"></script>
By including that file, which has closing script tags followed by opening script tags inside, this is the effective result:

<script language="javascript" type="text/javascript"
src="/wordpress/wp-content/themes/fjords01-10/js/all-spice.js">
<script type="text/javascript" language="JavaScript">
<!--
// Some code
//-->
</script>

<script type="text/javascript">
<!--
// Some code
//-->
</script>
<script type="text/javascript" language="JavaScript">
<!--
// Some code
//-->
</script>
<script type="text/javascript" language="javascript">
<!--
// Some code
//-->
</script>
</script>
So, you're effectively including javascript files which declare javascript html within themselves. Javascript doesn't halt on error so it shouldn't be much of a problem unless the tags break the parsing of the subsequent code.

Solution: Open wordpress/wp-content/themes/fjords01-10/js/all-spice.js and get rid of all the <script> and tags. Somehow I still doubt that will solve your problem, but it's a start.

Oh, and a statement is any command in Javascript. It could be something with parenthesis, or it could have an equals sign, but it's generally on its own line and has a semicolon on the end. Things like if(), for(), while(), else() are called case structures, and don't need semicolons, but generally have semicolons on the ends of the things inside them / after them. (Note: The semicolon is optional in Javascript!)

Christopher and 4evrblu no errors now with firebug. Yippee...

Funny thing is, as tremendously educational and eye opening as this thread is, has anyone noticed just how far off topic we have gotten. LOL

Funny.

Cuz' I originally asked if anyone could make sense out of my misbehaving style sheet and thumbnails. LOL

By the way, my thumbnails are still entirely style-less

:D

Good questions one and all.

One, the two styles you displayed were after the fact. Here is what I initially had instead of those two styles:

.highslide img {
border: 2px solid gray;
}
.highslide:hover img {
border: 2px solid white;
}

But those were not being called for some reason. Since the images appeared in .post, I thought I had better change it to something like:

.post .highslide img{
border: 2px solid gray;
}

.post .highslide:hover img{
border: 2px solid blue;
}

Only I was uncertain how to code it and in my confusion I totally muffed it, so the result is what you found.

I would like all the thumbnails within that particular post to look the same, with a 2 px border, grey, and a hover color of anything other than white. Maybe Gold or something. I dunno, just not white.

Does that help clear up the picture somewhat?

I haven't looked at the CSS but looking at the HTML, the original CSS was correct. At a guess, it probably wasn't working because something may have been over ruling it later on in the CSS file.

!important helps in these situations.

Try this:

a.highslide img {
border: 2px solid gray !important;
}

a.highslide:hover img {
border-color: blue !important;
}