Apple Safari and Dotnet

[Edward]

Hi All,

I feel frustrated with one of my Customers who wants me to ensure that a
dotnet web site I am building for them must be compatible to Apple's Safari
browser!

Safari is buggy and it does not support lots of things (xhtml etcc).

However, what puzzles me is that there are some dotnet Framework 2 web sites
out there that work perfectly well under Safari, whereas my website does not
while it is a simple one! I don't know what I am doing wrong and how those
sites manage to work ok.... so obviously Safari is not a limitation for
dotnet framework V2.

Is anyone able to explain to me if there is something that I can do to
ensure my site works under Safari?

Thank you so much.

Edward Re
Melbourne Australia

[Edward]

Hi Again,

I forgot to mention that my dotnet framework V2 web site uses the plainest
and simplest dotnet code (no javascript nor vb script) yet, it still FAILS
to render corrently under Safari! Looks like Safari does not handle too well
the <DIVelement!

thanks for your precious feedback

Edward

"Edward" <aR******@hotma il.comwrote in message
news:IR******** ***********@new s-server.bigpond. net.au...

Hi All,

I feel frustrated with one of my Customers who wants me to ensure that a
dotnet web site I am building for them must be compatible to Apple's
Safari browser!

Safari is buggy and it does not support lots of things (xhtml etcc).

However, what puzzles me is that there are some dotnet Framework 2 web
sites out there that work perfectly well under Safari, whereas my website
does not while it is a simple one! I don't know what I am doing wrong and
how those sites manage to work ok.... so obviously Safari is not a
limitation for dotnet framework V2.

Is anyone able to explain to me if there is something that I can do to
ensure my site works under Safari?

Thank you so much.

Edward Re
Melbourne Australia

[Chris Fulstow]

Can you give more specific information about how your application is
failing in Safari, and which controls you have used?

Edward wrote:

Hi Again,

I forgot to mention that my dotnet framework V2 web site uses the plainest
and simplest dotnet code (no javascript nor vb script) yet, it still FAILS
to render corrently under Safari! Looks like Safari does not handle too well
the <DIVelement!

thanks for your precious feedback

Edward

"Edward" <aR******@hotma il.comwrote in message
news:IR******** ***********@new s-server.bigpond. net.au...

Hi All,

I feel frustrated with one of my Customers who wants me to ensure that a
dotnet web site I am building for them must be compatible to Apple's
Safari browser!

Safari is buggy and it does not support lots of things (xhtml etcc).

However, what puzzles me is that there are some dotnet Framework 2 web
sites out there that work perfectly well under Safari, whereas my website
does not while it is a simple one! I don't know what I am doing wrong and
how those sites manage to work ok.... so obviously Safari is not a
limitation for dotnet framework V2.

Is anyone able to explain to me if there is something that I can do to
ensure my site works under Safari?

Thank you so much.

Edward Re
Melbourne Australia

[Edward]

sure.... if you have a look at http://www.gbab.net/ under Safari the
alignment of the <DIV>s to the right of the sidebar and the footer are all
over the place! The site looks super under Internet Explorer though!

Is any other info that I can provide for our investigation?

thanks for your time on this

Ed
"Chris Fulstow" <ch**********@h otmail.comwrote in message
news:11******** **************@ m7g2000cwm.goog legroups.com...

Can you give more specific information about how your application is
failing in Safari, and which controls you have used?

Edward wrote:

>Hi Again,

I forgot to mention that my dotnet framework V2 web site uses the
plainest
and simplest dotnet code (no javascript nor vb script) yet, it still
FAILS
to render corrently under Safari! Looks like Safari does not handle too
well
the <DIVelement!

thanks for your precious feedback

Edward

"Edward" <aR******@hotma il.comwrote in message
news:IR******* ************@ne ws-server.bigpond. net.au...

Hi All,

I feel frustrated with one of my Customers who wants me to ensure that
a
dotnet web site I am building for them must be compatible to Apple's
Safari browser!

Safari is buggy and it does not support lots of things (xhtml etcc).

However, what puzzles me is that there are some dotnet Framework 2 web
sites out there that work perfectly well under Safari, whereas my
website
does not while it is a simple one! I don't know what I am doing wrong
and
how those sites manage to work ok.... so obviously Safari is not a
limitation for dotnet framework V2.

Is anyone able to explain to me if there is something that I can do to
ensure my site works under Safari?

Thank you so much.

Edward Re
Melbourne Australia

[Mark Rae]

"Edward" <aR******@hotma il.comwrote in message
news:IR******** ***********@new s-server.bigpond. net.au...

I feel frustrated with one of my Customers who wants me to ensure that a
dotnet web site I am building for them must be compatible to Apple's
Safari browser!

I feel your pain! I went through precisely the same thing about a year
ago...

Safari is buggy and it does not support lots of things (xhtml etcc).

Actually, it isn't, and it does - you just have to know how...

That said, neither Safari nor Camino support styles on buttons - no-one has
ever been able to explain to me why this is!
However, there's no point trying - styles on buttons are simply ignored by
Safari and Camino.

However, what puzzles me is that there are some dotnet Framework 2 web
sites out there that work perfectly well under Safari, whereas my website
does not while it is a simple one! I don't know what I am doing wrong and
how those sites manage to work ok.... so obviously Safari is not a
limitation for dotnet framework V2.

Again, it's not the Framework per se...

Is anyone able to explain to me if there is something that I can do to
ensure my site works under Safari?

1 ) Choose the webpage which looks the worst in Safari :-)

2) Add the following code to the page's Page_PreInit method:

if (Request.Browse r.Browser.Conta ins("Safari"))
{
this.ClientTarg et = "uplevel";
}

How does it look now...?

[Edward]

Hello Mark,

I have made the change to the Pre Init method but I will have to get into
work first to test it, as I do not have a Mac here at home where I am now!
Here in Melbourne Ausrtalia it's close to 1AM, so I'll need to wait a few
hours to see if it works .....

I am keeping my fingetrs crossed that it works .... and if it does .... I'll
be a happy chappy! :-)

More to come.

Cheers

Ed
"Mark Rae" <ma**@markNOSPA Mrae.comwrote in message
news:%2******** ********@TK2MSF TNGP02.phx.gbl. ..

"Edward" <aR******@hotma il.comwrote in message
news:IR******** ***********@new s-server.bigpond. net.au...

>I feel frustrated with one of my Customers who wants me to ensure that a
dotnet web site I am building for them must be compatible to Apple's
Safari browser!

I feel your pain! I went through precisely the same thing about a year
ago...

>Safari is buggy and it does not support lots of things (xhtml etcc).

Actually, it isn't, and it does - you just have to know how...

That said, neither Safari nor Camino support styles on buttons - no-one
has ever been able to explain to me why this is!
However, there's no point trying - styles on buttons are simply ignored by
Safari and Camino.

>However, what puzzles me is that there are some dotnet Framework 2 web
sites out there that work perfectly well under Safari, whereas my website
does not while it is a simple one! I don't know what I am doing wrong and
how those sites manage to work ok.... so obviously Safari is not a
limitation for dotnet framework V2.

Again, it's not the Framework per se...

>Is anyone able to explain to me if there is something that I can do to
ensure my site works under Safari?

1 ) Choose the webpage which looks the worst in Safari :-)

2) Add the following code to the page's Page_PreInit method:

if (Request.Browse r.Browser.Conta ins("Safari"))
{
this.ClientTarg et = "uplevel";
}

How does it look now...?

[Mischa Kroon]

Also have a look at this:

http://slingfive.com/pages/code/browserCaps/

this can be used to replace the default browser detection code.

If you want a good idea of what the site looks like in safari you can boot
up a linux boot cd like knoppix and try looking at the site with konquerer
which uses an only slightly different browser engine.

Another option is using:
http://www.danvine.com/icapture/

Or another service like it :)


"Edward" <aR******@hotma il.comwrote in message
news:8F******** ***********@new s-server.bigpond. net.au...

Hello Mark,

I have made the change to the Pre Init method but I will have to get into
work first to test it, as I do not have a Mac here at home where I am now!
Here in Melbourne Ausrtalia it's close to 1AM, so I'll need to wait a few
hours to see if it works .....

I am keeping my fingetrs crossed that it works .... and if it does ....
I'll be a happy chappy! :-)

More to come.

Cheers

Ed
"Mark Rae" <ma**@markNOSPA Mrae.comwrote in message
news:%2******** ********@TK2MSF TNGP02.phx.gbl. ..

>"Edward" <aR******@hotma il.comwrote in message
news:IR******* ************@ne ws-server.bigpond. net.au...

>>I feel frustrated with one of my Customers who wants me to ensure that a
dotnet web site I am building for them must be compatible to Apple's
Safari browser!

I feel your pain! I went through precisely the same thing about a year
ago...

>>Safari is buggy and it does not support lots of things (xhtml etcc).

Actually, it isn't, and it does - you just have to know how...

That said, neither Safari nor Camino support styles on buttons - no-one
has ever been able to explain to me why this is!
However, there's no point trying - styles on buttons are simply ignored
by Safari and Camino.

>>However, what puzzles me is that there are some dotnet Framework 2 web
sites out there that work perfectly well under Safari, whereas my
website does not while it is a simple one! I don't know what I am doing
wrong and how those sites manage to work ok.... so obviously Safari is
not a limitation for dotnet framework V2.

Again, it's not the Framework per se...

>>Is anyone able to explain to me if there is something that I can do to
ensure my site works under Safari?

1 ) Choose the webpage which looks the worst in Safari :-)

2) Add the following code to the page's Page_PreInit method:

if (Request.Browse r.Browser.Conta ins("Safari"))
{
this.ClientTarg et = "uplevel";
}

How does it look now...?

[Edward]

I tried the code below and while it has improved the look and behaviour of
the menu control, the DIVs are still misbehaving:- they overlap whereas they
should lay one next to the other!

I would have thought Safari could understand DIV's being old contructs!

Help?

thanks

Ed
"Mark Rae" <ma**@markNOSPA Mrae.comwrote in message
news:%2******** ********@TK2MSF TNGP02.phx.gbl. ..

"Edward" <aR******@hotma il.comwrote in message
news:IR******** ***********@new s-server.bigpond. net.au...

>I feel frustrated with one of my Customers who wants me to ensure that a
dotnet web site I am building for them must be compatible to Apple's
Safari browser!

I feel your pain! I went through precisely the same thing about a year
ago...

>Safari is buggy and it does not support lots of things (xhtml etcc).

Actually, it isn't, and it does - you just have to know how...

That said, neither Safari nor Camino support styles on buttons - no-one
has ever been able to explain to me why this is!
However, there's no point trying - styles on buttons are simply ignored by
Safari and Camino.

>However, what puzzles me is that there are some dotnet Framework 2 web
sites out there that work perfectly well under Safari, whereas my website
does not while it is a simple one! I don't know what I am doing wrong and
how those sites manage to work ok.... so obviously Safari is not a
limitation for dotnet framework V2.

Again, it's not the Framework per se...

>Is anyone able to explain to me if there is something that I can do to
ensure my site works under Safari?

1 ) Choose the webpage which looks the worst in Safari :-)

2) Add the following code to the page's Page_PreInit method:

if (Request.Browse r.Browser.Conta ins("Safari"))
{
this.ClientTarg et = "uplevel";
}

How does it look now...?

[Mark Rae]

"Edward" <aR******@hotma il.comwrote in message
news:QO******** ***********@new s-server.bigpond. net.au...

>I tried the code below and while it has improved the look and behaviour of
the menu control, the DIVs are still misbehaving:- they overlap whereas
they should lay one next to the other!

I would have thought Safari could understand DIV's being old contructs!

Hmm - Safari is *VERY* XHTML

1) Are you writing your markup to XHTML-compliant standards and are you
using VS.NET 2005 to validate your markup properly?
Tools, Options, Text Editor, HTML, Validation, XHTML 1.0 / XHTML 1.1

2) Have you run your rendered markup through the XHTML validator?
http://validator.w3.org/

[Edward]

Hello Mark,

NO LUCK! I have made the page (www.gbab.net/zTest3.aspx) to be XHTML 1.0
compliant transitional using the http://validator.w3.org/ check syntax
parser and the necessary adjustments. I have also used the pre_init code
(this.ClientTar get = "uplevel";) HOWEVER the DIVs are still looking bad!

I don't understand why!

Maybe Safari does not apply the CSS properly to the DIVs.

I am determined to resolve this mystery though, I will keep on trying
different things.

Meanwhile, I appreciate immensely your help.

Edward
"Mark Rae" <ma**@markNOSPA Mrae.comwrote in message
news:OQ******** ******@TK2MSFTN GP04.phx.gbl...

"Edward" <aR******@hotma il.comwrote in message
news:QO******** ***********@new s-server.bigpond. net.au...

>>I tried the code below and while it has improved the look and behaviour of
the menu control, the DIVs are still misbehaving:- they overlap whereas
they should lay one next to the other!

I would have thought Safari could understand DIV's being old contructs!

Hmm - Safari is *VERY* XHTML

1) Are you writing your markup to XHTML-compliant standards and are you
using VS.NET 2005 to validate your markup properly?
Tools, Options, Text Editor, HTML, Validation, XHTML 1.0 / XHTML 1.1

2) Have you run your rendered markup through the XHTML validator?
http://validator.w3.org/