Wrox Home  
Search P2P Archive for: Go

  Return to Index  

aspdotnet_website_programming thread: Re: Macintosh, Windows 98 and Netscape


Message #1 by "Larkin Young" <youngld@j...> on Fri, 1 Nov 2002 00:20:30
> I have deployed a site largely based on techniques I learned from this 
b> ook.  Access is being allowed to about 100 people as a test.  All is 
well 
e> xcept that (1) 2 Windows 98 IE 5 users are getting Internet Explorer 
non-
r> ecoverable errors when they attempt to use a dropdown list, (3) a 
M> acintosh Internet Explorer 6 user is crashing on the use of any 
control, 
a> nd Netscape renders the login screen like it randomly scrambled the 
e> lements of a jigsaw puzzle.  
I> ?m wondering if there is something fundamental I don?t know about 
e> nabling access to machines other than Win 2K and XP.  Any ideas?
I>  absolutely love ASP.NET and C#.  I could never have done such a 
complex 
d> ata-intensive web site so rapidly using older technology, but I 
thought 
t> hat one of ASP.NET?s wonderful features was that it took care of 
browser 
d> ifferences for us developers who have better things to do.
T> he book is fantastic!  And this forum is marvelous.  Thanks.
P> ortia Isaacson, Future Computing


Portia, the steps Mike gave you are definitely a huge step in the right 
direction to take care of some of those other problems. As for netscape, 
i had the same issue. To resolve it, go into your application's 
web.config file and change the Response encoding to ASCII, as opposed to 
UTF-8..netscape does not like the utf-8 encoding, among many other 
standards they chose to ignore as well. But that should take care of your 
netscape problems.
-Larkin Young
Senior, Computer Science
James Madison University

Message #2 by "Larkin Young" <youngld@j...> on Fri, 1 Nov 2002 02:48:58
> > I have deployed a site largely based on techniques I learned from 
this 
b> > ook.  Access is being allowed to about 100 people as a test.  All is 
w> ell 
e> > xcept that (1) 2 Windows 98 IE 5 users are getting Internet Explorer 
n> on-
r> > ecoverable errors when they attempt to use a dropdown list, (3) a 
M> > acintosh Internet Explorer 6 user is crashing on the use of any 
c> ontrol, 
a> > nd Netscape renders the login screen like it randomly scrambled the 
e> > lements of a jigsaw puzzle.  
I> > ?m wondering if there is something fundamental I don?t know about 
e> > nabling access to machines other than Win 2K and XP.  Any ideas?
I> >  absolutely love ASP.NET and C#.  I could never have done such a 
c> omplex 
d> > ata-intensive web site so rapidly using older technology, but I 
t> hought 
t> > hat one of ASP.NET?s wonderful features was that it took care of 
b> rowser 
d> > ifferences for us developers who have better things to do.
T> > he book is fantastic!  And this forum is marvelous.  Thanks.
P> > ortia Isaacson, Future Computing

> 
P> ortia, the steps Mike gave you are definitely a huge step in the right 
d> irection to take care of some of those other problems. As for 
netscape, 
i>  had the same issue. To resolve it, go into your application's 
w> eb.config file and change the Response encoding to ASCII, as opposed 
to 
U> TF-8..netscape does not like the utf-8 encoding, among many other 
s> tandards they chose to ignore as well. But that should take care of 
your 
n> etscape problems.
-> Larkin Young
S> enior, Computer Science
J> ames Madison University


I should clarify here, after reading your posting. I misunderstood your 
problem with netscape. The issue i was referring to was with Netscape 
4.6+ I had problems where if you brought another window into focus on top 
of the netscape window for any reason the webpage would then display with 
all sorts of strange characters..something resembling an explosion of 
Wingdings on the page, hehe. In this case, changing the Response encoding 
to ASCII would solve the problem, I am surprised you haven't run into 
this issue with Netscape actually, I couldn't seem to avoid it until i 
discovered the solution. But I do think Mike is right about your jigsaw 
puzzle issue, and that is likely the MS_Positioning property of the Body 
tag in an aspx page. Personally, I think GridLayout is absolutely 
worthless, and causes more problems then not. It is merely an abstraction 
of using DHTML techniques to position elements on a page using absolute 
placementm which is always sketchy at best. You can be clever with 
flowlayout using tables and other spacer elements to create better 
control over how your page elements are rendered to the page. Anyways, 
sorry about the confusion, let me know if you have any questions.

-Larkin Young
Senior, Computer Science
James Madison University
Director, Technical Support Services, WildWires
(http://www.wildwiresonline.com)


  Return to Index