URGETN: Pages not loading for ie 5.0

[moondaddy]

I'm running an eCommerce site using vb.net 1.1 and frames. From the header
navigation frame I use the following client side JavaScript to navigate
pages in the frame below named 'main' which works good:

case "lblContactUs":
parent.main.document.location.href="ContactUs.aspx"
break;

however from the left frame I have menus that populate the main frame with
the ProductListing.aspx page which takes a parameter like this:

parent.main.document.location.href="ProductListing.aspx?MenuID=" + value;

and when I do this there's an error in the main frame which says something
about JavaScript. I haven't seen this myself, but this is the limited
description I have from a user.

Earlier I was getting complaints from users saying that they couldn't
navigate to any page and at that time all of my navigation used code like
this:

parent.main.frameElement.src="ProductListing.aspx?MenuID=" + value;

which works great in ie 6 but does nothing in older versions of ie and
Netscape.

How can I call a page in a different frame and pass in a parameter name and
value for older browsers?

Thanks.

 

[moondaddy]

Thanks Steven,
This information helps. Sorry for the late reply as I'm totally overwhelmed
right now. It turns out that about 20% of the browsers hitting the site are
4x Netscape which means I have to do a major re-write and fast. You
provided some good links below which I'll be using. Although they say
asp.net doesn't care what browser hits the site, that's not total true. For
example, Netscape 4x doesn't recognize style sheets, fonts in pixel sizes,
absolute positioning, and more. And I've kept nearly all of my style
formats in style sheets and classes.Uuuug. Anyway, thanks for the help!

--
(e-mail address removed)

Hi Moondaddy,

From your description, you've encountered some problems with browser
capability on frame based web pages, yes?

Your code indicate that you use javascript such as
"window.parent.framename.location.href"
or "window.parent.framename.document.location.href"
to set a frame's url from another frame.

As for this problem, I think the "window.parent.framename.location.href"
should be ok, also, you can try
"window.parent.frames[index].location.href" , use index to identify the
certain frame. I've made a test on my side via IE5 and it worked well. I've
attached my test pages in this message(three pages, one frame html page and
two aspx pages).

Also, I've found some references on using the Frameset (the document model
in netscape)
#FRAMES OF REFERENCES
http://developer.netscape.com/viewsource/archive/goodman_frames.html

#JavaScript Programmer's Reference - Netscape Navigator 2
http://www.irt.org/xref/nn_2.htm

And here are some other reference on Managing Browser Compatibility in
MSDNboth ASP or asp.net)

#Chapter 4: Managing Browser Compatibility
http://msdn.microsoft.com/library/en-us/dnproweb/html/chapter4managingbrowse

rcompatibility.asp?frame=true

http://msdn.microsoft.com/library/en-us/dnproweb/html/acompatibleframesetexa
mple.asp?frame=true

#Detecting Browser Capabilities(checking script engine in browser)
http://msdn.microsoft.com/library/en-us/jscript7/html/jsconDetectingBrowserC
apabilities.asp?frame=true


Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx

 

[Steven Cheng[MSFT]]

Thanks for your followup, Moondaddy,

Also, if you meet any new problems or need any assistance, please always
feel free to post here.


Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx