Fine in Explorer Not in Firefox

I’ve read some other posts and there are similar problems that seemed to indicate something CSS related but I wouldn’t know where to start.

Help

This could lead to problems. You have a few errors in layout, pay attention to the divs especially.

Thank you Jeremy Clark13,

Would that be divs in the posts I have added or something in the template I’m using. Is there a guide or validator that I could plug either in to give me an idea as to where I am going awry?

You can just check the view source box on the validatior page and then click on the each line error and it will show you where in your source the problem is.

Thank you Jeremy,

I went to https://validator.w3.org/ and entered the site https://validator.w3.org/check?uri=http%3A%2F%2Fwww.johnwade.ca%2Fblog_newsletter&charset=%28detect+automatically%29&doctype=Inline to discover errors. There were 29.

I believe I can correct many of them if I can find them. How do I determine which file in Theme editor to search for the problem line?

Shoot, forgot to mention. I discovered that if I enter in my browser a specific glog entry/page/post everything looks fine. It is only when I view my blog entries in their entirety that the problem occurs.

You’ll have to compare the files contents to the contents of the surrounding text of the error. It’s no easy answer you just have to look through all template files until you find where the error is occurring. In your case most of the errors are in post themselves, so you just have to edit the post instead of the actual template.

How do I determine which file in Theme editor to search for the problem line?

On the validator page check “Show Source” – then Revalidate.
Every line number becomes clickable…

Thank you Jeremy and moshu,

One of the errors contained a key word from an actual post, so I was able to view its html. However the error the validator provided doesn’t seem to be in the html.

The message and the html for the post follow:

Line 104, column 2: document type does not allow element “p” here; missing one of “object”, “applet”, “map”, “iframe”, “button”, “ins”, “del” start-tag .

<p><span style=”font-weight: bold”>Physical:</span></big><big> </big><big>Cushin

The mentioned element is not allowed to appear in the context in which you’ve placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you’ve forgotten to close a previous element.

One possible cause for this message is that you have attempted to put a block-level element (such as “<p>” or “<table>”) inside an inline element (such as ““, “<span>”, or “<font>”).

<big></big><big>
<span style=”font-weight: bold”>Behaviour:</span> The Canine Escape Artist</big> <big><small>Click Here for PDF File</small></big><big></big><big></big><span style=”font-weight: bold”><big>Physical:</big></span><big> </big><big>Cushings</big> <big><small>Click Here for PDF File</small></big><big></big><big></big>

<span style=”font-weight: bold”><big>Quotation:</big></span><big> <big>-</big> </big><big>Franklin P. Jones</big> <big>- <span style=”font-style: italic”>”Anybody that doesn’t know what soap tastes like has never washed a dog.”</span></big><big></big><big></big>

<span style=”font-weight: bold”><big>John’s Pet Talk Column:</big></span><big> </big><big>Syndicated through SunMedia and also available on-line on Canoe’s Lifewise website.</big> <big><small> Click Here to Visit Pet Talk with John Wade</small></big><big></big><big></big>

<span style=”font-weight: bold”><big>Train Your Dog With John Wade:</big></span><big> 10 Days With John on a Board and Train May be Just the Ticket for That Dog That Won’t Come or Walk Nicely</big> <small><big>Click Here to Learn More</big></small><big></big><big></big>

<span style=”font-weight: bold”><big>Humor:</big></span><big><big><img src=”https://www.johnwade.ca/blog_newsletter/Images/Dog_Sign_Vancouver.jpg&#8221; alt=”Dog_Sign_Vancouver.jpg” title=”Dog_Sign_Vancouver.jpg” align=”left” border=”0″ height=”367″ hspace=”5″ vspace=”5″ width=”261″ /></big></big>

<big><big> </big></big>

john

Looking at that output it shows me one more reason why the wysiwyg editor should be banned ??
All those million big-big tags are inserted by the wysiwyg editor when you try to “style” your text in posts…
It will be a nightmare to clean them up.

Now that’s encouraging ?? I’m afraid the wysiwyg editor exists for people like me, wyhgachtdio, (When You Haven’t Got A Clue How To Do It Otherwise.) :)I tried to download a program called CSE html validator in hopes it might do some clean up but it won’t install.

My posts are usually very short and are all identical as far as content and formatting. The only content that changes each month is a small amount of text. So I suppose I can work on one and then make the changes in the other with the other as a guide.

I take it I should learn about replacing the <big> nonsense with an actual font size?

Honestly? I have never seen a dedicated person who couldn’t learn to use the Quicktags in a half hour – with the wysiwyg totally disabled.
Using quicktags you have great chances to write posts without validation issues.
Just my $0.02.

Thank you Moshu,

I think I can do that. I’ve just had a look. I didn’t know it coded it differently. However, I don’t see a tag for font size.

IMO using inline ‘font-size’ style is a very bad practice. Want bigger fonts? – set the general fontsize for posts bigger.
For emphasizing: use <strong> and <em> ( with the B and I quicktags).

In extraordinary cases you can use span class="whatever" and define the class(es) in your stylesheet. It is cleaner.

Thank you Moshu,

Some of the free html editors have their own version of quicktags do they not? If so are you familiar with one you would recommend.