Asp.net for safari browser?

[Paul W]

Hi - can someone point me to info on the issues/resolutions of supporting
the safari browser?

To help me understand, if I was developing pages in say FrontPage, what
attributes would I set for 'target browser'?

I'm having a helluva time with table layouts etc and goin' stir crazy..

Thanks, Paul.

 

[clintonG]

These resources [1],[2] should help you out.

<%= Clinton Gallagher
METROmilwaukee (sm) "A Regional Information Service"
NET csgallagher AT metromilwaukee.com
URL http://metromilwaukee.com/
URL http://clintongallagher.metromilwaukee.com/

[1] http://www.garykeith.com/browsers/
[2]
http://staff.develop.com/ballen/blog/PermaLink.aspx?guid=1bf2016a-d8b5-48f1-b37a-a2b01f5f8cff

 

[Juan T. Llibre]

Pauk,

See : http://word.mvps.org/MacWordNew/

Apparently, later versions of Safari are a bit buggy,
and cannot handle HTML 4.0 as well as they should.

Safari version 1.2.2. (build 125.7) and later have some issues.

There's quite a few versions of Safari :
http://developer.apple.com/internet/safari/uamatrix.html

I'd check to see the level of support which Safari's different versions have,
and make a decision as to which versions of Safari you'll support.

Supporting them all will be a nightmare.


As far as the "target browser", that won't do very much unless
you can pin down Safari's exact capabilities, so you can create
an intelligent browsercaps definition for it.

You could setup a clientTarget element, per :
http://msdn.microsoft.com/library/d...us/cpgenref/html/gngrfClientTargetElement.asp
but doing that for the different flavors of Safari
will keep you working for quite a while.

Maybe a good way to make sure Safari can read your pages would be
to check Apple's recommendations for building web pages, particularly
the XHTML section, which both Safari and Visual Studio support :

http://developer.apple.com/internet/webcontent/bestwebdev.html

Smart use of CSS classes will help a lot, too.
Again, both Safari and VS.NET support it. See the above doc.

Maybe this will help you, maybe not.
If you want to support Safari, you'll have to sweat hard anyway.

Now for the bad as of ASP.NET 2.0, the whole browser
discovery/capability assigning paradigm changes once more,
so we'll have to relearn everything.

 

[clintonG]

Nice job of scaring the hell out of everybody Juan

Do you have any references to the 2.0 changes you referred to? This MSDN
article [1] is all I have so far.

<%= Clinton Gallagher

[1] http://msdn.microsoft.com/msdnmag/issues/05/01/ASPColumn/default.aspx

 

[Juan T. Llibre]

I should have added that you must save
the attachment first, and then view it with
Notepad++, Notepad or any plain text reader.

heh, heh...

The sidebar in the article link you sent,
has very good information of the details :

http://msdn.microsoft.com/msdnmag/issues/05/01/ASPColumn/default.aspx?side=true#a

All the browser information is removed from machine.config,
and is replaced by *.browser files which define the browsers.

"the machine-wide files are in the browsers subdirectory of the
.NET Framework configuration directory, and application-specific
files can be placed in a directory under the Web application root
with the same name ( /browsers )."

"One of the key changes in this version of the browserCaps feature is that
the .browser files are used to generate code for a factory type that, given
an HttpRequest, will produce an HttpBrowserCapabilities object.

In the previous version, the regular expressions were processed
in the order that they were parsed from the configuration files.

Take a look at the attached "ie.browser" file, and you'll see
how all the IE browsers are condensed into the one browser file.

It's easier to modify, since you can just add whatever new capabilities
a new browser version has by adding an updated tag and its capability.

For example :

<capability name="css1" value="true" />
<capability name="css2" value="true" />

To identify a browser, just ID it :

<browser id="IE6to9" parentID="IE5to9">
<identification>
<capability name="majorversion" match="[6-9]" />
</identification>

That will ID IE versions 6 through 9.

Working with browser elements and gateway elements,
make this system a lot simpler, and easier to program.

Give that article a thorough reading. It's spot on.

For more Beta 2 and later info, see :

http://msdn2.microsoft.com/library/3yekbd5b(en-us,vs.80).aspx
http://msdn2.microsoft.com/library/x3k2ssx2(en-us,vs.80).aspx
http://msdn2.microsoft.com/library/0hyey391(en-us,vs.80).aspx ( JScript )

In code, the HttpCapabilitiesBase class is used :
http://msdn2.microsoft.com/library/5e2aew0b(en-us,vs.80).aspx

Here's how to detect whether a browser's IE, for example :

http://msdn2.microsoft.com/library/0zsyfcee(en-us,vs.80).aspx

Have fun!

Nice job of scaring the hell out of everybody Juan

Do you have any references to the 2.0 changes you referred to? This MSDN
article [1] is all I have so far.

<%= Clinton Gallagher

[1] http://msdn.microsoft.com/msdnmag/issues/05/01/ASPColumn/default.aspx

Pauk,

See : http://word.mvps.org/MacWordNew/

Apparently, later versions of Safari are a bit buggy,
and cannot handle HTML 4.0 as well as they should.

Safari version 1.2.2. (build 125.7) and later have some issues.

There's quite a few versions of Safari :
http://developer.apple.com/internet/safari/uamatrix.html

I'd check to see the level of support which Safari's different versions
have,
and make a decision as to which versions of Safari you'll support.

Supporting them all will be a nightmare.


As far as the "target browser", that won't do very much unless
you can pin down Safari's exact capabilities, so you can create
an intelligent browsercaps definition for it.

You could setup a clientTarget element, per :
http://msdn.microsoft.com/library/d...us/cpgenref/html/gngrfClientTargetElement.asp
but doing that for the different flavors of Safari
will keep you working for quite a while.

Maybe a good way to make sure Safari can read your pages would be
to check Apple's recommendations for building web pages, particularly
the XHTML section, which both Safari and Visual Studio support :

http://developer.apple.com/internet/webcontent/bestwebdev.html

Smart use of CSS classes will help a lot, too.
Again, both Safari and VS.NET support it. See the above doc.

Maybe this will help you, maybe not.
If you want to support Safari, you'll have to sweat hard anyway.

Now for the bad as of ASP.NET 2.0, the whole browser
discovery/capability assigning paradigm changes once more,
so we'll have to relearn everything.







Hi - can someone point me to info on the issues/resolutions of supporting
the safari browser?

To help me understand, if I was developing pages in say FrontPage, what
attributes would I set for 'target browser'?

I'm having a helluva time with table layouts etc and goin' stir crazy..

Thanks, Paul.