Forum Moderators: open
[ewages.cjb.net...]
Only this one page on this browser is corrupted and missing...it works everywhere else.
Thanks for any help::I hope I'm in the right place.
A couple of things come to mind.
1. You should define the js function from within the HEAD, not between the HEAD and FRAMESET
2. You're closing the script tag twice
2. A META REFRESH in NOFRAMES isn't valid
3. The NOFRAMES section belongs nested inside the FRAMESET tags.
A good place to check your code is with the W3C Validator [validator.w3.org] You'll be amazed at how much homework that can give you!
I took at look at your site in both IE 5.5 and NN4.79. The NN version did indeed not show on the support page.
I have a few comments which you might find useful.
I'm not sure why you are using framsets since you are copying the navigation system into a main frame. usually a frame set is used in order to not need to load that code again.
I would run the resultant HTML through a validator to see what is going on. The code looks good to me, but I make mistakes too.
Also, I was baffled by the download request from Gator. What was that for? I don't like getting popups from any site I visit, let alone one that asks me to download stuff.
The site looks very nice, BTW. I hope you can fix the problem.
In general Netscape is much more picky about syntax than IE. IE will let you slide with quite a mess, but NN needs everything in order.
I didn't think about this before I posted::
The frames your seeing must be what cjb.net uses to show the site. cjb.net is the free hosting service the site is on::the reason for that bloody gator pop-up as well.
Could it just be NN4.x browsers though? I see no reason why the form shouldn't show up, I use the same exact form at catalystnetwork.com and it's fine on NN 4.77.
One last possibly absurd question. Could it have anything to do with cjb.net's frameset and it's reaction to NN4.x browsers? I didn't write the frameset but it is basically housing my page on the web.
Thanks again
Madcat
<tr><td>
<a href="foo">link text<a href="foo2"></a>
</td></tr>
The code opens a second anchor tag before it closes the first one, and therefore an anchor is open across the </td></tr> -- Netscape gets crazy when a table structure isn't perfect.
That is worth a shot for sure. I will go and fix these and see if they're the problem childs. thanx
txbakers::
I only use it so I can throw up comps to the client before I move their files to the server. I know it is annoying to have those pop-ups, but they're only temporary.
You can put up as many CJB.Nets as you want for free.
If you get your page to validate by the W3C, then you can be pretty sure that's the problem.
BTW, I assume you didn't put the link fix online, because I still see the same issue -- beginning on line 54.