Firefox - IE  Incompatibility Problem (SOLVED)

bob3160 · 2007-03-10T23:53:53.000Z

I seem to have an incompatibility problem between the two browsers on the following
website I set up for the Meadow Lake Residents Association
When opened with IE or IE compatibility mode in FF, the items in the left column are all selectable links.
If, however, I open this website using Firefox, only the last 2 items in the left column are selectable links.
Flock appears to have the same problem as Firefox.
I can however use Opera without any problems… ??? ??? ???

Can any one figure this out?
Thanks

polonus · 2007-03-11T00:14:20.000Z

Hi bob3160,

This has nothing to do with the browser used, but follows from the location from where you try to access this webcontent and the settings there, try to use a proxy like http://www.backfox.com or http://www.boxofprox.com/cgi.shtml and you see it is the local settings from googlepages that cause your predicament or try another than http://72.14.203.104/
All been OK here from Europe when I looked it up in Flock or IE7.

greets,

polonus

DavidR · 2007-03-11T00:43:19.000Z

No problems from my end using firefox, dial-up, no proxy.

No Script temporarily allowed for relevant scripts.

FreewheelinFrank · 2007-03-11T10:41:14.000Z

Hi Bob,

The page contains quite a few coding errors at the moment. This from the W3C Markup Validation Service:

http://validator.w3.org/check?uri=http%3A%2F%2Fmlra.newmexico.googlepages.com%2Fhome

This from Dreamweaver validation test:

Validator Results

Report date: March 11 2007
Report time: 09:07:12
Severity File Description Line
Error Bob’s page The tag: “meta” has an XML style closing syntax for an empty element even though version: “HTML20” is not an XML tag language. 6
Message Bob’s page in tag: script the following required attributes are missing: type 544
Error Bob’s page The tag:“div” is not allowed within: “h1” It is only allowed within: button, del, fieldset, iframe, ins, noframes, noscript, object, td, th. 553
Nesting Bob’s page tag: " div" invalid inside tag: “p”. " p" closing tag is optional. Validation will proceed as if context is closed. 555
Nesting Bob’s page No starting tag found for: “p”, or it was closed too many times 557
Error Bob’s page The tag: “a” doesn’t have an attribute: “imageanchor” in currently active versions. 564
Error Bob’s page The tag: “img” doesn’t have an attribute: “galleryimg” in currently active versions. 564
Error Bob’s page The tag: “img” doesn’t have an attribute: “km” in currently active versions. 564
Error Bob’s page The tag: “a” doesn’t have an attribute: “imageanchor” in currently active versions. 565
Message Bob’s page In HTML 4.0, FONT is deprecated. It may become obsolete in future versions, consider using style sheets instead. 567
Error Bob’s page The tag: “hr” has an XML style closing syntax for an empty element even though version: “HTML4” is not an XML tag language. 585
Nesting Bob’s page tag: " div" invalid inside tag: “p”. " p" closing tag is optional. Validation will proceed as if context is closed. 586
Nesting Bob’s page No starting tag found for: “p”, or it was closed too many times 588

Error/Warning Type Count
Total errors: 7
Total warnings: 0
Total nesting errors: 4
Total messages: 2

Using Dreaweaver revealed a object in front of the unclickable links. Removing this made the links clickable in Firefox:

http://geocities.com/dontsurfinthenude/bobspage.htm

IE and Opera were probably being unduly flattering to the page; Firefox rendered it more honestly, including the errors. If the page is tidied up, it will work fine in any browser: there’s no need to ask your viewers to use IE.

EDIT:

Tidy Online also reveals some problems with the page:

Errors and Warnings

line 544 column 3 - Warning: lacks “type” attribute
line 553 column 31 - Warning:

isn’t allowed in

elements
line 553 column 49 - Warning: missing

before

line 553 column 127 - Warning: discarding unexpected
line 554 column 36 - Warning: trimming empty

line 555 column 34 - Warning: trimming empty

line 555 column 61 - Warning: trimming empty

line 557 column 81 - Warning: replacing element

by

line 557 column 81 - Warning: inserting implicit

line 558 column 36 - Warning: trimming empty

line 564 column 276 - Warning: unknown attribute “km”
line 564 column 276 - Warning: unknown attribute “galleryimg”
line 564 column 276 - Warning: lacks “alt” attribute
line 565 column 63 - Warning: trimming empty

line 565 column 333 - Warning: lacks “alt” attribute
line 569 column 36 - Warning: trimming empty

line 579 column 38 - Warning: trimming empty

line 587 column 12 - Warning: trimming empty

line 587 column 34 - Warning: trimming empty

line 589 column 114 - Warning: replacing element

by

line 589 column 114 - Warning: inserting implicit

line 590 column 34 - Warning: trimming empty

line 594 column 3 - Warning: discarding unexpected

line 597 column 27 - Warning: trimming empty
line 597 column 66 - Warning: trimming empty
line 598 column 27 - Warning: trimming empty
line 598 column 66 - Warning: trimming empty
line 600 column 27 - Warning: trimming empty
line 600 column 66 - Warning: trimming empty
29 warnings/errors were found!

The alt attribute should be used to give a short description
of an image; longer descriptions should be given with the
longdesc attribute which takes a URL linked to the description.
These measures are needed for people using non-graphical browsers.

You are recommended to use CSS to specify the font and
properties such as its size and color. This will reduce
the size of HTML files and make them easier maintain
compared with using elements.

http://valet.htmlhelp.com/tidy/

bob3160 · 2007-03-11T18:14:45.000Z

Thank you all. Especially Frank for all the effort you put into this.
It’s obvious from going to the page you created (except for the missing picture link)
that the errors are on my end.
Unfortunately I don’t have the skill or knowledge to make the corrections.
The page was built with the Google Page builder and someplace during all the edits that I’ve made, something
got screwed up. It may not be right, but at least it’s still there.
If I attempt to make any of the suggested changes, (I don’t really have a clue how) I may no longer have a website… :‘( :’(
Guess for now, It will just have to stay the way it is.

Again, thanks for the help.

FreewheelinFrank · 2007-03-11T20:36:01.000Z

Bob,

The picture is missing because I didn’t put the picture on my site: if you upload the page to your site, you will see the picture.

The page got a little messed up in the title section, although it now displays correctly. The other things are just a bit of tidying up to comply with W3C standards.

I’ll tidy up the page for you and post a link to it: you can view the page source and save it in your normal HTML editor.

EDIT: This won’t work with the Geocities link above because Yahoo! adds advertising scripts: use the links below.

PS: How is the title section meant to look. At the moment it’s:

Main title
Blue bar
Sub title

Is this how you intended it, or was the blue bar meant to include either or both of the titles?

FreewheelinFrank · 2007-03-11T22:20:12.000Z

Here’s the tidied up page:

bobspage.htm

Some of the image attributes were not valid HTML. If these are removed, the page is Valid HTML 4.01 Transitional:

bobspage2.htm

(These attributes may be required for the page to display correctly on googlepages.com.)

If the title is not as you intended, let me know.

EDIT: Here’s another option:

bobspage3.htm

bob3160 · 2007-03-12T02:37:39.000Z

Thanks for all your effort Frank but when I try to plug this into Google,
it just doesn’t come out right.
For now, I’ll just have to leave well enough alone.
Again, thanks for all the help.

bob3160 · 2007-03-12T02:42:29.000Z

I have noticed one thing:
In the tidied up page that you prepared, all links are selectable.
If you click on the home page link however, you’re right back in the same catch 22. ??? ???

FreewheelinFrank · 2007-03-12T08:50:53.000Z

When you click on the home page link, the link is to:

http://mlra.newmexico.googlepages.com/home,

not to my page.

You need to change the name of my file (bobspage.htm) to the name of your home page file and upload it to Google and test it there.

Quite possibly Google depends on some non-standard code in the page, so try this page, in which I’ve done the bare minimum, just removing the offending object.

bobspage4.htm

bob3160 · 2007-03-13T16:00:52.000Z

Thank You Frank
I was finally able to find the offending object within the original website
while using the html function of Google Page Creator which was the only way to edit the “home” page.
Once I removed it, all the links sprang back to life.

For all the Firefox users, the incompatibility was mine not the browsers. ;D

FreewheelinFrank · 2007-03-13T17:45:56.000Z

Thank You Frank

No problem.

I can confirm the page is now working OK in Firefox.

Announcements