http://validator.w3.org/check?uri=http://www.madpc.co.uk/~peterv/

Without a Parse Model or a proper Doctype declaration you are forcing web browsers to operate in the quirks mode - where the browser has to guess how you intend the web page to be rendered. It ain't gonna "guess" with any consistency, it may appear slightly different for each person who views the page.
http://en.wikipedia.org/wiki/Quirks_Mode

"So I am delaying upgrading. "
Did you create your website solely for your own viewing pleasure? If not, do you expect your viewers to use specific browsers to view your website, or use an older web browser just to view your website?

AFA Claris Home Page 3 - it's what, 14 years old?
http://lowendmac.com/musings/03/0219.html

Dan Knight - 2003.02.19 - Tip Jar

Claris Home Page was one of the finest applications ever made for the Mac. Version 3.0 has been around since 1998, and a lot of us have yet to find a better program for writing and publishing on the Web.

That's a shame, because the Web and Internet standards have progressed quite a bit over the past five years - and Home Page doesn't support most of those changes. 

http://bluegriffon.org/
BlueGriffon is a new WYSIWYG content editor for the World Wide Web. Powered by Gecko, the rendering engine of Firefox, it's a modern and robust solution to edit Web pages in conformance to the latest Web Standards.

Thanks for chipping in folks. I've come across the 'Validator' before which throws up loads of errors on all sorts of web pages, not just mine, but which work perfectly satisfactorily.

Maybe I'll try Blue Griffon. No doubt yet another steep learning curve :-( And Home Page is soooo easy to use! The point really is why does my code or rather Claris' code work fine in the earlier version of Firefox, in Netscape Navigator and in a recent version of Internet Explorer, but not in the latest version of Firefox?? Many people have web sites several years old - if Firefox now refuses to recognise older code does this mean people will have to rehash their web sites just to make them useable?

Cheers, Peter.

That is a removed (missing) CSS rule in resource://gre-resources/html.css that was there in Firefox 3.6 to add a border to images.
So you will have to add it yourself.

In Firefox 3.6.28, line 416:

• Fx 3.6: resource://gre/res/html.css
• Fx 13: resource://gre-resources/html.css

*|*:-moz-any-link img, img[usemap], object[usemap] {
  border: 2px solid;
}

Thank you very much indeed, cor-el. So there IS an unfriendly change in Firefox. I don't have the skills or the software to change and recompile Firefox. I hope one of the developers (you?) acts on this and restores the missing rule in the next version. Then I'll be only too happy to upgrade ;-) I much prefer Firefox to Internet Explorer having followed the Netscape route over the years, and owe the developers of Netscape, Firefox and Thunderbird a huge vote of thanks.

To answer the-edmeister's question, yes of course my web site is for other people to view. And it does view correctly in Internet Explorer and earlier versions of Firefox. Maybe I should try it in Google Chrome (which I'd have to install) - if the borders work there as well, then I can approach the comment from the other end - why should I have to learn a new program and rebuild web pages, some of which are over 10 years old and have worked perfectly all those years, so that they will work in a specific browser?

I should mention that the links still work and the cursor changes when over the linked image, so all is not lost ;-)

Cheers, Peter.

Web standards is the reason you should fix your pages. The web hasn't stood still over the last 10 years, even Microsoft is following "standards" these days. I truly doubt that your pages "worked perfectly" all that time, in all web browsers, without conforming to those "standards" - to wit, the lack of Doctype and parsing tags.

http://www.w3.org/

Hi, 'ed'.

Well, I've done a few tests. The border does not appear in Google Chrome :-(

So I installed and tried Blue Griffon. Very simply - just placed a small image on a new page, and linked it to a larger version. In both versions of Firefox and in IE (I'd uninstalled Chrome by this time) the border was almost invisible and didn't change colour after the linked image was visited. So much for new software! (Although to be fair in my very brief encounter it looks reasonably easy to use.) If I loaded an existing page into BG and saved it there was no change. To 'fix' my pages it looks as though I'd have to start from scratch. No way!!

So although the border isn't visible in later versions of Firefox the links work fine. I guess I'll stick with Claris, and hope that for the most part browsers remain backwardly compatible. Although I dislike IE - like most Microsoft offerings it tries to take over control, at least it still shows my web pages correctly! If it ain't broke....

Cheers, Peter.

Just re-add the missing CSS rule to your website if you want a border around images.

img { border: 2px solid; }

Or if you only want the border on images that are links, you could use this rule:

a img {border-width:2px}

It might be beneficial to create an external style sheet and link it into your pages now. Then as you are transitioning to a more modern design, you can add new rules globally with a single change. Not sure whether the Claris software can do this for you, or you'd have to add the link tag yourself.

Thanks guys,

I'm not familiar with direct HTML , so not sure how the code should be entered, but I've tried a number of different 'containers' A,P etc. and Claris alters the code every time usually showing it as an anchor.

But even if I find the correct method and it works, presumably I'd have to apply it to every individual htm page where I have images. That's 100+. And if every image, out of the question as you'll see if you visit my web site.

http://www.madpc.co.uk/~peterv

I still have to ask why the line originally referred to by cor-el has been omitted from later versions of Firefox. As I've already stated, the automatic border on linked images still appears as expected in IE 9. And underlining of linked text is still correct in Firefox 13.

Cheers,

Peter

Hi petevasey, there are two steps. First, create a new text file named something like style.css and put your style rule in it. Second, add this line to the <head> section of each page:

<link rel="stylesheet" href="style.css" type="text/css">

If Claris has the concept of a template that applies changes to each page, then it should be easy. Otherwise, it is a lot of edits.

As for why it changed, there might be a record of that in Bugzilla, the bug reporting system, but I think you are the first person I've seen who wanted the border. Every other post I've seen asked how to get rid of it.

Finally, please note that your pages render in "quirks" mode because they do not have a document type declaration at the top. Quirks mode is a non-standard legacy mode that each browser handles a bit differently.

More info on standards/quirks:

• http://www.quirksmode.org/css/quirksmode.html
• http://en.wikipedia.org/wiki/Quirks_mode

Note: I do not suggest changing the rendering mode of all your pages at once because that almost certainly will increase the length of your "to do" list. If you upgrade your editor to a more modern one, that would be a good time to consider the change.

Well, I'm very grateful to all you folks who have chipped in - thank you for your interest. It would seem that the problem is not so much down to my old style Home Page coding but because 'automatic' image bordering has been left out of some browsers on purpose. Personally I find it a useful indication that an image is linked. But of course floating the cursor over the image also gives an indication as it changes shape.

I don't propose to start adding code manually to my pages - a lot of work, and I don't really know what I'm doing - without someone looking over my shoulder to give me exact coding I'd probably get it wrong and maybe break my pages.

Hopefully 'Quirks' mode will continue to be part of modern browsers to allow old fogies like me to use Home Page and keep my web site on line for others to (also hopefully!) enjoy. If I eventually find an up-to-date web page builder which is as easy to use as Home Page, then who knows what the future holds!

Thanks again,

Peter.