Hello Beverly,
Thanks for posting in the group.
Firstly, please use a simple page to reproduce the problem and then view source to find out which part causes the difference.
If there is no way to change output, my suggestion would be to render different outputs to different browsers. You could add
runat="server" to the BODY tag, then add a reference in your code-behind to the ID you assigned to the BODY tag declaring
the control as an HtmlGenericControl. Then in your code behind, you can do the following...
Assuming your BODY tag in the ASPX page looks like:
<body id="myBody" runat="server">
Your code-behind could do the following:
myBody.Attributes["bgColor"] = "#003366";
You can find out what browser they are using with the Request.Browser object.
You can specify which browser you'd like to target the HTML output toward by using the Page.ClientTarget property.
By the way, you could also paste Netscape related browser issues at:
http://devedge.netscape.com/community/newsgroups/
Hope that helps.
Best regards,
Yanhong Huang
Microsoft Online Partner Support
Get Secure! -
www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
!Content-Class: urn:content-classes:message
!From: "beverly" <
[email protected]>
!Sender: "beverly" <
[email protected]>
!Subject: netscape 7.1 colors
!Date: Tue, 19 Aug 2003 08:09:19 -0700
!Lines: 5
!Message-ID: <
[email protected]>
!MIME-Version: 1.0
!Content-Type: text/plain;
! charset="iso-8859-1"
!Content-Transfer-Encoding: 7bit
!X-Newsreader: Microsoft CDO for Windows 2000
!X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
!Thread-Index: AcNmY9zwhEfiWpkBTOutCW1X8vYbMw==
!Newsgroups: microsoft.public.dotnet.general
!Path: cpmsftngxa06.phx.gbl
!Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.general:105016
!NNTP-Posting-Host: TK2MSFTNGXA11 10.40.1.163
!X-Tomcat-NG: microsoft.public.dotnet.general
!
!I have a .net application that works great in IE,
!however, in Netscape 7.1 the background colors are not
!comparable to IE. Has anybody else experienced this? If
!so, have you found a solution that does not interfer with
!IE?
!