ASP.NET and Netscape

[sunaj]

Hi,

I would like my asp.net web page to work for everybody - not just members of the Microsoft clan

Just a simple thing like defining the width of a textbox (which is no problem with a HTML <input type=&quot;text&quot;>), is not straightforward. I soon discovered that .net renders HTML 4.0 for IE, but 3.2 for all other browsers. After some research I also found out that the problem could be eliminated by telling .net to render HTML 4.0 to other browsers as well, by adding something like
-------------------------
<browserCaps>
<result type=&quot;System.Web.HttpBrowserCapabilities, System.Web, Version=1.0.3102.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a&quot; />
<use var=&quot;HTTP_USER_AGENT&quot; />
TagWriter=System.Web.UI.HtmlTextWriter
</browserCaps>
--------------------------
to the web.config file.

Unfortunately this causes the nonsence (for me at least) error:
Type 'System.Web.HttpBrowserCapabilities' does not inherit from 'System.Web.Mobile.MobileCapabilities'.

HELP!


Sunaj
'The gap between theory and practice is not as wide in theory as it is in practice'

 

[jzelhart]

Since you didn't get any responses yesterday, here is my two cents. Probably too simple but...

I change my Target Schema to:

Internet Explorer 3.02 / Netscape Navigator 3.0

This helped my users that don't use the latest copy of Internet Explorer.

Hope this helps.

Hope everyone is having a great day!

Thanks - Jennifer

 

[sunaj]

Thx Jennifer - but not exactly what I was looking for.
I find it hard to believe that there is not a proper solution for this problem. That makes ASP.net close to worthless (unless you know that all your users use Microsoft)...
At least you could control things in ASP even though it came out a little messy.

Sunaj
'The gap between theory and practice is not as wide in theory as it is in practice'

 

[crazyboybert]

Can't offer a solution to this but can give you my thoughts on the matter....In my opinion where possible we should all be using XHTML1.0 to render our pages in line with w3c standards. One of my biggest dissappointments with .NET has been the complete inconsistency of HTML code that different controls render. The mix of font tags and css styles, tables and divs is awful. However, on a brighter note it appears ASP.NET2.0 will give full XHTML1.0 support so these could be woes of the past before too long...

In terms of using an older spec for your target schema, with all due respect to others right to choose their own methods I believe this to be wrong. Why should a website dumb-down its functionality, accesibility, performance and standards compliance for the sake of all those old, out of date, quirky browsers. Should everyone get the same experience as the lowest common denominator just because some have lagged behind? It's the developers responsibility to provide the best experience possible to the largest majority whilst ensuring graceful degradation for the minority of users who don't have version 5 or above browsers...

I guess i'm a bit of a standards puritan though so thsi could be a bit of a biased view ;-)

Rob

Go placidly amidst the noise and haste, and remember what peace there may be in silence - Erhmann 1927

 

[sunaj]

Everybody conforming to one standard - now wouldn't that be nice!
I was very exited at first with ASP.NET, because I think they solved they 'event driven' controls in a nice way. What I did not realize (that is until now) that it comes at a very high price, namely lost control of how your HTML renders. I don't see why it not possible to have both.
I will let my optimism prevail and trust that these problems are solved in ASP.NET2.0!

Sunaj
'The gap between theory and practice is not as wide in theory as it is in practice'