Macintosh asp .net 1

[cosmoh2o]

I have had great help in the past with the members of tek-tips so I hope that they can provide some answers to the problem I am having now. I have recently built a asp .net web program that runs VB .NET and it works perfectly on a Windows PC, the problem is that some of the users have macintosh (9.X - OS X). The macintosh systems can log into the web page but somewhere in the progress the pages the web page(s) freeze up.

For example:
log on to

http://www.x.com

brings page x.aspx up. You select "next" button and user is brought to x2.aspx, and so on. At no clearly defined point the new page is NOT served on a Macintosh (works fine on PC). I am passing Session variables to each page.

If anyone out there has any ideas, I would appreciate it. Thanks a million.

 

[jfrost10]

Are you using any of the IE web controls on your aspx pages?

It could be there's something thats MS only, and buggering up the Mac browser. Which browser on the Mac's are you using?

D'Arcy

 

[cosmoh2o]

I am using Internet Explorer on Macintosh.

 

[qwert231]

I have customers having the same problem. I think it is a combo box I am using, third party. They use IE and Netscape.

 

[dragonwell]

I've seen somethign like this too. It appears that IE on the mac caches more than on windows, and does not check for updated versions as often as you would think. So, in some cases, the viewstate the user got during one view gets cached on their mac and, now that you've made a change to the controls of the page, their viewstate is invalid and thus corrupt. The mac user will probably need to delete their "temporary internet files" or whatever they're called on mac.

Another issue is the implmentation of javascript in ie for mac is a little differnet than ion ie for windows, so certain cleint-side events might not work as expected, such as clicking a linkbutton (versus clicking a href type link). I have seen this too, but not very often.

HTH

David

 

[cosmoh2o]

Thanks to everybody for the responses. I've checked around and this does seem to be a common problem. Feels good to not be the only one experiencing this issue.

 

[cosmoh2o]

found the problem. I was transfering session variable data with Response.Redirect("page.aspx&quot instead of Server.Transfer("page.aspx&quot. The Response.Redirect method "pings" the client browser for information about the page redirection and this is no problem except with the macintosh explorer browsers. The Server.Transfer method works just fine.
Thanks to all for the help.