Re: DotNet & Netscape4

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: amos (soma_at_caramail.com)
Date: 09/30/04 

Date: 30 Sep 2004 09:25:22 -0700

Hi

it has nothing to see with the encoding, I made several tests,
but I think know where it comes from after all those tests.

It comes from the instruction that writes in a layer.

You can put in any HTML section of your ASPX page a LAYER,
then try to write in it, and you'll see that if you take
the same code in a HTML or ASP classic page, it works,
and it won't work in the ASPX page.

You can only make the test on a NETSCAPE4 browser since
it is the only one that accepts LAYERS.

When I look at the source code generated in Netscape,
the code is EXACTLY THE SAME that I entered.

So the only thing is that a page generated by ASPX
maybe goes in a different part of the memory and when
you use the write method, it makes everything bugging.

It's surely a bug from Netscape4 but with a link with
dotnet because in a page generated in ASP, it works.

"Patrice" <nobody@nowhere.com> wrote in message news:<e82QPetpEHA.4076@TK2MSFTNGP12.phx.gbl>...
> And of course, use entities for characters or save the page as utf-8
> encoded.
>
> You could also do the other way round and change the web.config file to
> reflect your prefered charset :
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/html/gngrfglobalizationsection.asp
>
> Hope it helps.
>
> Patrice
>
> --
>
> "Patrice" <nobody@nowhere.com> a écrit dans le message de
> news:evbUZ4spEHA.3592@TK2MSFTNGP14.phx.gbl...
> > Ok, with such a background, you should understand that ASP.NET doesn't
> come
> > in play once the HTML code moved to the browser.
> >
> > From the description of the problem (you didn't mentionned exactly in your
> > first post), this is likely an encoding problem. When ASPX sends the file,
> > it sends an encoding information in the HTTP header. The one that is in
> your
> > file conflict with information.
> >
> > To test remove the "meta" from your HTML file. Does it work ? Let us know.
> >
> > Patrice
> > --
> >
> > "amos" <soma@caramail.com> a écrit dans le message de
> > news:dd140c27.0409291442.6afdcab1@posting.google.com...
> > > In fact, I post this here because I would like that the Microsoft
> > > developers take care of a few things for the version 2.0 of the
> > > framework (and I know they read those newsgroups).
> > >
> > > For example, the session timeouts that don't work well (but this is
> > > another point..)
> > >
> > >
> > > So, to come back to my point, I'll try to be clear. I know this is a
> > > bug from DOTNET, I develop for more than 10 years, and I don't annoy
> > > people for nothing.
> > >
> > >
> > > Okay, so try to make this example :
> > >
> > > make an .aspx very simple with a ILAYER in it with a 'this is a test'
> > > text inside the ILAYER.
> > >
> > > Then, make a button or a select that changes the 'this is a test' in
> > > 'hello world' (with the write method, the only one that works to
> > > change the content of an ILAYER).
> > >
> > > Compile the .aspx and look at it in Netscape 4 (the only spread
> > > browser that accepts layers).
> > >
> > > You'll see that when you want to change the content of the layer with
> > > the button or the select, you'll have a lot of weird caracters that
> > > will appear on the screen (caracters like squares).
> > >
> > > Now, make view source on netscape, and copy the source the .aspx page
> > > has generated into a HTML blank page that you will create.
> > >
> > > Now, you agree that the .HTML page and the .ASPX will be the same.
> > >
> > > And you'll see that the code will work properly, which is normal,
> > > because you know how to program in javascript, so the source code
> > > works.. but only with a .html extension ..
> > >
> > > Am I Clear now ?
> > >
> > > So the bug can only come from the DOTNET motor that interfers with
> > > Netscape4 when you use the .write method in a ILAYER (I think it
> > > writes in a part of netscape memory).
> > >
> > > So what can look like a little bit 'light' for a Microsoft developer
> > > to look at it, is still that strange that it may occurs in other
> > > places and in other browsers, and I think it's good to know why this
> > > bugs so we have a version 2.0 of dotnet that is the less buggy
> > > possible.
> > >
> > > Thanks by advance for reading my all stuff.
> > >
> > > If you want to download Netscape 4, you can go to ftp.netscape.com in
> > > the pub folder.
> > >
> > >
> > >
> > >
> > > "Patrice" <nobody@nowhere.com> wrote in message
> news:<uwt12DlpEHA.1160@tk2msftngp13.phx.gbl>...
> > > > Similar or exactly the same ?
> > > >
> > > > ASP.NET doesn't have anything to do client side. If the source is the
> same
> > > > it should work the same. The only things that annoys me a bit is that
> the
> > > > default encoding for ASP.NET is utf-8 while you are using another
> encoding.
> > > > It could perhaps mess the JavaScript but likely not up to this
> point...
> What
> > > > is the exact behavior you see ? (Javascript doesn't work nut not error
> ?)
> > > >
> > > > Unfortunately I don't have NS4 handy.
> > > >
> > > > Let us know.
> > > >
> > > > Patrice
> > > >
> > > > --
> > > >
> > > > "amos" <soma@caramail.com> a écrit dans le message de
> > > > news:dd140c27.0409290953.1e2bc86c@posting.google.com...
> > > > > The source is SIMILAR
> > > > >
> > > > > ..
> > > > >
> > > > > that's why the question remains .. unsolved
> > > > >
> > > > > "Patrice" <nobody@nowhere.com> wrote in message
> news:<eJ13QthpEHA.2304@TK2MSFTNGP14.phx.gbl>...
> > > > > > Just check the source client side ("view source" or similar) to
> see
> if
> it's
> > > > > > different.
> > > > > >
> > > > > > Let us know.
> > > > > >
> > > > > > Patrice
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > "amos" <soma@caramail.com> a écrit dans le message de
> > > > > > news:dd140c27.0409290314.78949a72@posting.google.com...
> > > > > > > Don't give me lessons, take a big breath, read slowly and put
> your
> ego
> > > > > > > of speed thinker on the side (I talk to the first guy of
> Microsoft
> who
> > > > > > > answers the question) but try to understand the question :
> > > > > > >
> > > > > > > When you use ILAYERS a LAYERS in Netscape 4 and you try to write
> in it
> > > > > > > any text with the open and write methods (like if you use
> innerHTML &
> > > > > > > SPAN for other browsers), it will work in HTML or ASP, but the
> code
> > > > > > > will not work properly when compiled by the dotnet motor on
> ASPX.
> > > > > > >
> > > > > > > To test this, use the code I gave or any other code that writes
> in
> a
> > > > > > > LAYER,
> > > > > > > and view it in NETSCAPE 4 in HTML classic and in a ASPX page you
> > > > > > > compiled.
> > > > > > >
> > > > > > > You'll see somthing really amazing that is a bug I think (I hope
> > > > > > > not..) of DOT NET :
> > > > > > >
> > > > > > > The two pages you'll see (the .HTML classic and the .ASPX) have
> the
> > > > > > > same source (type view source in NETSCAPE4), but the one with
> the
> > > > > > > .HTML extension works and the one with .ASPX bugs
> > > > > > >
> > > > > > > I think you guys with Microsft should look at this problem
> closer
> > > > > > > before releasing the version 2.0 of the framework.
> > > > > > >
> > > > > > >
> > > > > > > Anyway thank you by advance for any help.
> >
> >

Quantcast