The Glade 4.0

http://www.rorinthas.com/gladepbp/ crashes in the newest version of internet Explorer.

Any ideas on how to fix it?

Seems to work on Crome, but i'd rather figure out how to make it work. If you can't view the page because of the problem and want to help I can provide you the sources.

Edit- Acutally on Chrome another feature (linking to the A #Targs) appears to be broken but at least the page doesn't crash

_________________
I prefer to think of them as "Fighting evil in another dimension"

IE is just getting overloaded, man. Few problems..

Using Framesets, a deprecated element.
Loading 12 IFrames inside of said Frameset
Loading 23 javascripts inside each IFrame.

This site is just begging to choke, man.

I'd suggest hosting the scripts yourself, only loading them one time, and using something like a JQuery smooth-scrolling script for the anchor links. The framesets and hundreds of script loads need to go.

I'll see what I can do. It just bugs me that it's worked fine for the last three years

_________________
I prefer to think of them as "Fighting evil in another dimension"

I can't exactly see what's going on right now since I'm getting internal PHP errors from all content on thetangledweb.net. I strongly suspect Lenas is correct, though. 12x23 (=276) <script> elements is asking for trouble in IE. Apart from its functional problems, IE's javascript engine is just extremely slow. Expect it to choke on javascript loads that other browsers can handle.

Nevertheless, you should ditch the <iframe> elements for design reasons. Just let your site be an index for the content on the other pages. Iframes are:

• unnecesssary, especially with the advent of tabbed browsers
• deprecated. Frames are banned in both the Strict and Transitional doctypes for HTML 4.01 (1999!) and XHTML. They're banned entirely from HTML 5
• bad for usability and accessibility
• arguably rude to the content's host when you embed someone else's pages in your own. The situation is a bit like image leeching, only less subtle.
• overly complicated. They make troubleshooting site errors and peculiar browser behavior considerably more complicated to debug

With respect to the last point, this is probably why your links aren't working in Chrome -- at least in part.

You're linking across iframe boundaries, and to an empty anchor at that. Technically, neither of these are illegal, but it's a funky operation. I'm not that surprised that some browsers (especially a work in progress) are confused by this. It will probably work in Chrome, but your HTML needs to be completely correct. You can start by adding a doctype declaration to your page. Since you're using frames, you'll have to stick to the HTML 4.01 Frameset DTD:


This will change how your browser interprets the HTML, and may let it be more "frames aware". Now that you have a doctype, you can validate your page and fix the errors. There are a number of things that need to be fixed. Offhand, I see that all of your element names are in caps. Even though most browsers ignore that, it isn't legal HTML. More importantly, you have unquoted attribute names here and there. In particular, the "target" attribute of the "a" elements in header.html:


"List" needs to be in double (preferred) or single quotes to be valid HTML. This will probably fix the linking problem in Chrome. If the target frame isn't set right, this could easily explain why Chrome is having trouble. While we're on the topic, it's recommend (but not required) that you use all lower-case attribute names.

Whether or not the above works, I would also recommend that you not use empty anchors in list.html. If nothing else, empty anchors are non-semantic. They hurt usability/accessibility, especially for text browsers, and they can hork more subtle things like search engine indexing. Try something like:



Optionally, you can then style the "internal" class to not appear as a normal link with underlining, etc. That might not be necessary since it doesn't have an "href" attribute, though. I think most browsers will treat such anchors as "invisible".

_________________
Sail forth! steer for the deep waters only!
Reckless, O soul, exploring, I with thee, and thou with me;
For we are bound where mariner has not yet dared to go,
And we will risk the ship, ourselves and all.

Forgot to include this link:

http://validator.w3.org/

You can use that to validate your HTML if you don't feel like getting your own. There are also a number of good validator plugins for Firefox, most of them based on HTML TIDY.

The standalone Tidy app is pretty slick. It can validate, fix (usually), and "pretty-print" your HTML in one fell swoop. I use it religiously on every page I code.

_________________
Sail forth! steer for the deep waters only!
Reckless, O soul, exploring, I with thee, and thou with me;
For we are bound where mariner has not yet dared to go,
And we will risk the ship, ourselves and all.