By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
458,107 Members | 1,617 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 458,107 IT Pros & Developers. It's quick & easy.

DotNet & Netscape4

P: n/a
Hi

I'm experiencing a real nasty thing about dotnet.

I've made a big application in dotnet and I would like
to use ILAYERS for netscape 4.

You CAN NOT USE Layers and Form buttons in Netscape 4
if you save your page in .aspx

Try to save the following code in .html and in .aspx
then look at those two pages in Netscape 4 :

<script language=javascript>
function ChangeIntitule()
{
if (document.Form1.Origine.selectedIndex==0)
stringX="";
if (document.Form1.Origine.selectedIndex==1)
stringX="Exemple: '1992-1998 : Ecole supérieure d'art dramatique de Paris'";
if (document.Form1.Origine.selectedIndex==2)
stringX="Exemple: '2002 : Sara Pearson, Patrik Widrig (Contact Improvisation)'";
if (document.Form1.Origine.selectedIndex==3)
stringX="Exemple: '2003 : Cinéma - Film Snatch - figuration 3 jours'";
if (document.Form1.Origine.selectedIndex==4)
stringX="Exemple: 'Mime', 'Pianiste', 'Trapeziste', etc..";
if (document.Form1.Origine.selectedIndex==5)
stringX="Exemple: 'yoga', 'photographie', 'sculpture', etc..";

if (document.layers){

document.countdownnsmain.document.countdownnssub.d ocument.write(stringX);
document.countdownnsmain.document.countdownnssub.d ocument.close();
}
else if (document.all||document.getElementById)
crosscount.innerHTML=stringX;
}
</script>

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<form name=Form1>
<select name="Origine" id="Origine" class="letras" onchange="ChangeIntitule();">
<option value="-1">Choisissez une rubrique</option>
<option value="0">Etudes / Formation Artistique</option>
<option value="1">Stage / Séminaire</option>
<option value="2">Expérience professionnelle</option>
<option value="3">Activité Artistique</option>
<option value="4">Loisirs</option>

</select><input type=text name=sqdf>
</form>
<form name=qsd>
<ilayer id="countdownnsmain" width=300; height=50; visibility=show>
<layer id="countdownnssub" width=300; height=50; left=0 top=0> </layer>
</ilayer>
</form>
You'll see that all the codes that you wrote for Netscape4 whith
the ILAYERS don't work if you save the page as .aspx.
IS THIS A HUGE BUG OF DOT NET ????????
Nov 18 '05 #1
Share this Question
Share on Google+
29 Replies


P: n/a
> IS THIS A HUGE BUG OF DOT NET ????????

No. It's a huge gap in your understanding of ASP.Net.

ASP.Net is a technology which is chiefly used to create HTML documents
dynamically. What the HTML content of those documents is ENTIRELY UP TO YOU.
There are no restrictions. You have total control. You control the
horizontal. You control the vertical. Therefore, if you write an ASP.Net app
such that the HTML it spits out isn't working in a particular browser, YOU
made a mistake.

In conclusion:

A little learning is a dang'rous thing. Drink deep, or taste not the Pierian
spring. (Alexander Pope)

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
I get paid good money to
solve puzzles for a living

"amos" <so**@caramail.com> wrote in message
news:dd**************************@posting.google.c om...
Hi

I'm experiencing a real nasty thing about dotnet.

I've made a big application in dotnet and I would like
to use ILAYERS for netscape 4.

You CAN NOT USE Layers and Form buttons in Netscape 4
if you save your page in .aspx

Try to save the following code in .html and in .aspx
then look at those two pages in Netscape 4 :

<script language=javascript>
function ChangeIntitule()
{
if (document.Form1.Origine.selectedIndex==0)
stringX="";
if (document.Form1.Origine.selectedIndex==1)
stringX="Exemple: '1992-1998 : Ecole supérieure d'art dramatique de Paris'"; if (document.Form1.Origine.selectedIndex==2)
stringX="Exemple: '2002 : Sara Pearson, Patrik Widrig (Contact Improvisation)'"; if (document.Form1.Origine.selectedIndex==3)
stringX="Exemple: '2003 : Cinéma - Film Snatch - figuration 3 jours'";
if (document.Form1.Origine.selectedIndex==4)
stringX="Exemple: 'Mime', 'Pianiste', 'Trapeziste', etc..";
if (document.Form1.Origine.selectedIndex==5)
stringX="Exemple: 'yoga', 'photographie', 'sculpture', etc..";

if (document.layers){

document.countdownnsmain.document.countdownnssub.d ocument.write(stringX);
document.countdownnsmain.document.countdownnssub.d ocument.close();
}
else if (document.all||document.getElementById)
crosscount.innerHTML=stringX;
}
</script>

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<form name=Form1>
<select name="Origine" id="Origine" class="letras" onchange="ChangeIntitule();"> <option value="-1">Choisissez une rubrique</option>
<option value="0">Etudes / Formation Artistique</option>
<option value="1">Stage / Séminaire</option>
<option value="2">Expérience professionnelle</option>
<option value="3">Activité Artistique</option>
<option value="4">Loisirs</option>

</select><input type=text name=sqdf>
</form>
<form name=qsd>
<ilayer id="countdownnsmain" width=300; height=50; visibility=show>
<layer id="countdownnssub" width=300; height=50; left=0 top=0> </layer>
</ilayer>
</form>
You'll see that all the codes that you wrote for Netscape4 whith
the ILAYERS don't work if you save the page as .aspx.
IS THIS A HUGE BUG OF DOT NET ????????

Nov 18 '05 #2

P: n/a
And what's the error/issue specifically?
This is all clientside scripting, not sure what it has to do with server
coding?

--
Curt Christianson
Owner/Lead Developer, DF-Software
Site: http://www.Darkfalz.com
Blog: http://blog.Darkfalz.com
"amos" <so**@caramail.com> wrote in message
news:dd**************************@posting.google.c om...
Hi

I'm experiencing a real nasty thing about dotnet.

I've made a big application in dotnet and I would like
to use ILAYERS for netscape 4.

You CAN NOT USE Layers and Form buttons in Netscape 4
if you save your page in .aspx

Try to save the following code in .html and in .aspx
then look at those two pages in Netscape 4 :

<script language=javascript>
function ChangeIntitule()
{
if (document.Form1.Origine.selectedIndex==0)
stringX="";
if (document.Form1.Origine.selectedIndex==1)
stringX="Exemple: '1992-1998 : Ecole supérieure d'art dramatique de
Paris'";
if (document.Form1.Origine.selectedIndex==2)
stringX="Exemple: '2002 : Sara Pearson, Patrik Widrig (Contact
Improvisation)'";
if (document.Form1.Origine.selectedIndex==3)
stringX="Exemple: '2003 : Cinéma - Film Snatch - figuration 3 jours'";
if (document.Form1.Origine.selectedIndex==4)
stringX="Exemple: 'Mime', 'Pianiste', 'Trapeziste', etc..";
if (document.Form1.Origine.selectedIndex==5)
stringX="Exemple: 'yoga', 'photographie', 'sculpture', etc..";

if (document.layers){

document.countdownnsmain.document.countdownnssub.d ocument.write(stringX);
document.countdownnsmain.document.countdownnssub.d ocument.close();
}
else if (document.all||document.getElementById)
crosscount.innerHTML=stringX;
}
</script>

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<form name=Form1>
<select name="Origine" id="Origine" class="letras"
onchange="ChangeIntitule();">
<option value="-1">Choisissez une rubrique</option>
<option value="0">Etudes / Formation Artistique</option>
<option value="1">Stage / Séminaire</option>
<option value="2">Expérience professionnelle</option>
<option value="3">Activité Artistique</option>
<option value="4">Loisirs</option>

</select><input type=text name=sqdf>
</form>
<form name=qsd>
<ilayer id="countdownnsmain" width=300; height=50; visibility=show>
<layer id="countdownnssub" width=300; height=50; left=0 top=0> </layer>
</ilayer>
</form>
You'll see that all the codes that you wrote for Netscape4 whith
the ILAYERS don't work if you save the page as .aspx.
IS THIS A HUGE BUG OF DOT NET ????????

Nov 18 '05 #3

P: n/a
> IS THIS A HUGE BUG OF DOT NET ????????

DotNet, by default, doesn't really go out of its way to write valid markup
or cross-browser client side scripts for you. If that's a big concern, then
that's something you need to tweak yourself when writing your own HTML
output controls.

-Darrel
Nov 18 '05 #4

P: n/a
If you've added the client-side JavaScript yourself and it doesn't work,
it's because there is a problem with the script. VS.NET doesn't change your
client-side script.
"amos" <so**@caramail.com> wrote in message
news:dd**************************@posting.google.c om...
Hi

I'm experiencing a real nasty thing about dotnet.

I've made a big application in dotnet and I would like
to use ILAYERS for netscape 4.

You CAN NOT USE Layers and Form buttons in Netscape 4
if you save your page in .aspx

Try to save the following code in .html and in .aspx
then look at those two pages in Netscape 4 :

<script language=javascript>
function ChangeIntitule()
{
if (document.Form1.Origine.selectedIndex==0)
stringX="";
if (document.Form1.Origine.selectedIndex==1)
stringX="Exemple: '1992-1998 : Ecole supérieure d'art dramatique de
Paris'";
if (document.Form1.Origine.selectedIndex==2)
stringX="Exemple: '2002 : Sara Pearson, Patrik Widrig (Contact
Improvisation)'";
if (document.Form1.Origine.selectedIndex==3)
stringX="Exemple: '2003 : Cinéma - Film Snatch - figuration 3 jours'";
if (document.Form1.Origine.selectedIndex==4)
stringX="Exemple: 'Mime', 'Pianiste', 'Trapeziste', etc..";
if (document.Form1.Origine.selectedIndex==5)
stringX="Exemple: 'yoga', 'photographie', 'sculpture', etc..";

if (document.layers){

document.countdownnsmain.document.countdownnssub.d ocument.write(stringX);
document.countdownnsmain.document.countdownnssub.d ocument.close();
}
else if (document.all||document.getElementById)
crosscount.innerHTML=stringX;
}
</script>

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<form name=Form1>
<select name="Origine" id="Origine" class="letras"
onchange="ChangeIntitule();">
<option value="-1">Choisissez une rubrique</option>
<option value="0">Etudes / Formation Artistique</option>
<option value="1">Stage / Séminaire</option>
<option value="2">Expérience professionnelle</option>
<option value="3">Activité Artistique</option>
<option value="4">Loisirs</option>

</select><input type=text name=sqdf>
</form>
<form name=qsd>
<ilayer id="countdownnsmain" width=300; height=50; visibility=show>
<layer id="countdownnssub" width=300; height=50; left=0 top=0> </layer>
</ilayer>
</form>
You'll see that all the codes that you wrote for Netscape4 whith
the ILAYERS don't work if you save the page as .aspx.
IS THIS A HUGE BUG OF DOT NET ????????

Nov 18 '05 #5

P: n/a
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.
Nov 18 '05 #6

P: n/a
Just check the source client side ("view source" or similar) to see if it's
different.

Let us know.

Patrice
--

"amos" <so**@caramail.com> a écrit dans le message de
news:dd**************************@posting.google.c om...
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.

Nov 18 '05 #7

P: n/a
The source is SIMILAR

...

that's why the question remains .. unsolved

"Patrice" <no****@nowhere.com> wrote in message news:<eJ**************@TK2MSFTNGP14.phx.gbl>...
Just check the source client side ("view source" or similar) to see if it's
different.

Let us know.

Patrice
--

"amos" <so**@caramail.com> a écrit dans le message de
news:dd**************************@posting.google.c om...
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.

Nov 18 '05 #8

P: n/a
TJS
I think it does not work because you have two forms in your html. In aspx,
pages are treated as postback and only use 1 form.
"amos" <so**@caramail.com> wrote in message
news:dd**************************@posting.google.c om...
Hi

I'm experiencing a real nasty thing about dotnet.

I've made a big application in dotnet and I would like
to use ILAYERS for netscape 4.

You CAN NOT USE Layers and Form buttons in Netscape 4
if you save your page in .aspx

Try to save the following code in .html and in .aspx
then look at those two pages in Netscape 4 :

<script language=javascript>
function ChangeIntitule()
{
if (document.Form1.Origine.selectedIndex==0)
stringX="";
if (document.Form1.Origine.selectedIndex==1)
stringX="Exemple: '1992-1998 : Ecole supérieure d'art dramatique de Paris'"; if (document.Form1.Origine.selectedIndex==2)
stringX="Exemple: '2002 : Sara Pearson, Patrik Widrig (Contact Improvisation)'"; if (document.Form1.Origine.selectedIndex==3)
stringX="Exemple: '2003 : Cinéma - Film Snatch - figuration 3 jours'";
if (document.Form1.Origine.selectedIndex==4)
stringX="Exemple: 'Mime', 'Pianiste', 'Trapeziste', etc..";
if (document.Form1.Origine.selectedIndex==5)
stringX="Exemple: 'yoga', 'photographie', 'sculpture', etc..";

if (document.layers){

document.countdownnsmain.document.countdownnssub.d ocument.write(stringX);
document.countdownnsmain.document.countdownnssub.d ocument.close();
}
else if (document.all||document.getElementById)
crosscount.innerHTML=stringX;
}
</script>

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<form name=Form1>
<select name="Origine" id="Origine" class="letras" onchange="ChangeIntitule();"> <option value="-1">Choisissez une rubrique</option>
<option value="0">Etudes / Formation Artistique</option>
<option value="1">Stage / Séminaire</option>
<option value="2">Expérience professionnelle</option>
<option value="3">Activité Artistique</option>
<option value="4">Loisirs</option>

</select><input type=text name=sqdf>
</form>
<form name=qsd>
<ilayer id="countdownnsmain" width=300; height=50; visibility=show>
<layer id="countdownnssub" width=300; height=50; left=0 top=0> </layer>
</ilayer>
</form>
You'll see that all the codes that you wrote for Netscape4 whith
the ILAYERS don't work if you save the page as .aspx.
IS THIS A HUGE BUG OF DOT NET ????????

Nov 18 '05 #9

P: n/a
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" <so**@caramail.com> a écrit dans le message de
news:dd**************************@posting.google.c om...
The source is SIMILAR

..

that's why the question remains .. unsolved

"Patrice" <no****@nowhere.com> wrote in message

news:<eJ**************@TK2MSFTNGP14.phx.gbl>...
Just check the source client side ("view source" or similar) to see if it's different.

Let us know.

Patrice
--

"amos" <so**@caramail.com> a écrit dans le message de
news:dd**************************@posting.google.c om...
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.

Nov 18 '05 #10

P: n/a
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" <no****@nowhere.com> wrote in message news:<uw**************@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" <so**@caramail.com> a écrit dans le message de
news:dd**************************@posting.google.c om...
The source is SIMILAR

..

that's why the question remains .. unsolved

"Patrice" <no****@nowhere.com> wrote in message

news:<eJ**************@TK2MSFTNGP14.phx.gbl>...
Just check the source client side ("view source" or similar) to see if it's different.

Let us know.

Patrice
--

"amos" <so**@caramail.com> a écrit dans le message de
news:dd**************************@posting.google.c om...
> 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.

Nov 18 '05 #11

P: n/a
No, I only have one form ..

THe problem does not come from the source that works properly, it
comes from an interference from netscape4 & dotnet ..

For example, another point that is strange, when you make a
Response.redirect, in Netscape 4, sometimes, the navigator put a blank
page with a link which is (THE PAGE HAS MOVED HERE) and when you click
on the link, you go to the page that has been redirected.. but this is
not the problem that I want to fix today
"TJS" <no****@here.com> wrote in message news:<#p**************@TK2MSFTNGP10.phx.gbl>...
I think it does not work because you have two forms in your html. In aspx,
pages are treated as postback and only use 1 form.
"amos" <so**@caramail.com> wrote in message
news:dd**************************@posting.google.c om...
Hi

I'm experiencing a real nasty thing about dotnet.

I've made a big application in dotnet and I would like
to use ILAYERS for netscape 4.

You CAN NOT USE Layers and Form buttons in Netscape 4
if you save your page in .aspx

Try to save the following code in .html and in .aspx
then look at those two pages in Netscape 4 :

<script language=javascript>
function ChangeIntitule()
{
if (document.Form1.Origine.selectedIndex==0)
stringX="";
if (document.Form1.Origine.selectedIndex==1)
stringX="Exemple: '1992-1998 : Ecole supérieure d'art dramatique de

Paris'";
if (document.Form1.Origine.selectedIndex==2)
stringX="Exemple: '2002 : Sara Pearson, Patrik Widrig (Contact

Improvisation)'";
if (document.Form1.Origine.selectedIndex==3)
stringX="Exemple: '2003 : Cinéma - Film Snatch - figuration 3 jours'";
if (document.Form1.Origine.selectedIndex==4)
stringX="Exemple: 'Mime', 'Pianiste', 'Trapeziste', etc..";
if (document.Form1.Origine.selectedIndex==5)
stringX="Exemple: 'yoga', 'photographie', 'sculpture', etc..";

if (document.layers){

document.countdownnsmain.document.countdownnssub.d ocument.write(stringX);
document.countdownnsmain.document.countdownnssub.d ocument.close();
}
else if (document.all||document.getElementById)
crosscount.innerHTML=stringX;
}
</script>

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<form name=Form1>
<select name="Origine" id="Origine" class="letras"

onchange="ChangeIntitule();">
<option value="-1">Choisissez une rubrique</option>
<option value="0">Etudes / Formation Artistique</option>
<option value="1">Stage / Séminaire</option>
<option value="2">Expérience professionnelle</option>
<option value="3">Activité Artistique</option>
<option value="4">Loisirs</option>

</select><input type=text name=sqdf>
</form>
<form name=qsd>
<ilayer id="countdownnsmain" width=300; height=50; visibility=show>
<layer id="countdownnssub" width=300; height=50; left=0 top=0> </layer>
</ilayer>
</form>
You'll see that all the codes that you wrote for Netscape4 whith
the ILAYERS don't work if you save the page as .aspx.
IS THIS A HUGE BUG OF DOT NET ????????

Nov 18 '05 #12

P: n/a
Hi,

I gave the code you posted a spin. I don't have Netscape 4.? (there are
about 17 versions of 4 if you include the betas). I do have Netscape 7.1
and your code didn't work in that as a .html or a .aspx file. Can you test
on 7.1 if your code works for you. If it does please repost the entire code
page you are using. The code you posted before has two forms in it, no
<HTML> tag, no <HEAD> tag and no <BODY> tag, so who knows what is all going
on in your page. Just post the entire .html file you are using from the
first line to the last and we'll see if we can figure something out. I have
a pretty good idea that this has nothing to do with ASP.Net and everything
to do with Netscape 4. In your last reply to Patrice you felt that when
hitting an ASPX page the .write method of iLayer was writing to Netscape
memory. I highly doubt this, but if it is the case then we should figure it
out before someone actually learns how to use it to take over any
unsuspecting Netscape 4 users out there. Good luck! Ken.

--
Ken Dopierala Jr.
For great ASP.Net web hosting try:
http://www.webhost4life.com/default.asp?refid=Spinlight

"amos" <so**@caramail.com> wrote in message
news:dd**************************@posting.google.c om...
No, I only have one form ..

THe problem does not come from the source that works properly, it
comes from an interference from netscape4 & dotnet ..

For example, another point that is strange, when you make a
Response.redirect, in Netscape 4, sometimes, the navigator put a blank
page with a link which is (THE PAGE HAS MOVED HERE) and when you click
on the link, you go to the page that has been redirected.. but this is
not the problem that I want to fix today
"TJS" <no****@here.com> wrote in message

news:<#p**************@TK2MSFTNGP10.phx.gbl>...
I think it does not work because you have two forms in your html. In aspx, pages are treated as postback and only use 1 form.
"amos" <so**@caramail.com> wrote in message
news:dd**************************@posting.google.c om...
Hi

I'm experiencing a real nasty thing about dotnet.

I've made a big application in dotnet and I would like
to use ILAYERS for netscape 4.

You CAN NOT USE Layers and Form buttons in Netscape 4
if you save your page in .aspx

Try to save the following code in .html and in .aspx
then look at those two pages in Netscape 4 :

<script language=javascript>
function ChangeIntitule()
{
if (document.Form1.Origine.selectedIndex==0)
stringX="";
if (document.Form1.Origine.selectedIndex==1)
stringX="Exemple: '1992-1998 : Ecole supérieure d'art dramatique de

Paris'";
if (document.Form1.Origine.selectedIndex==2)
stringX="Exemple: '2002 : Sara Pearson, Patrik Widrig (Contact

Improvisation)'";
if (document.Form1.Origine.selectedIndex==3)
stringX="Exemple: '2003 : Cinéma - Film Snatch - figuration 3 jours'";
if (document.Form1.Origine.selectedIndex==4)
stringX="Exemple: 'Mime', 'Pianiste', 'Trapeziste', etc..";
if (document.Form1.Origine.selectedIndex==5)
stringX="Exemple: 'yoga', 'photographie', 'sculpture', etc..";

if (document.layers){

document.countdownnsmain.document.countdownnssub.d ocument.write(stringX); document.countdownnsmain.document.countdownnssub.d ocument.close();
}
else if (document.all||document.getElementById)
crosscount.innerHTML=stringX;
}
</script>

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <form name=Form1>
<select name="Origine" id="Origine" class="letras"

onchange="ChangeIntitule();">
<option value="-1">Choisissez une rubrique</option>
<option value="0">Etudes / Formation Artistique</option>
<option value="1">Stage / Séminaire</option>
<option value="2">Expérience professionnelle</option>
<option value="3">Activité Artistique</option>
<option value="4">Loisirs</option>

</select><input type=text name=sqdf>
</form>
<form name=qsd>
<ilayer id="countdownnsmain" width=300; height=50; visibility=show>
<layer id="countdownnssub" width=300; height=50; left=0 top=0> </layer> </ilayer>
</form>
You'll see that all the codes that you wrote for Netscape4 whith
the ILAYERS don't work if you save the page as .aspx.
IS THIS A HUGE BUG OF DOT NET ????????

Nov 18 '05 #13

P: n/a
There is no reason for you to be rude.

My response to your post had nothing to do with ego, so put your hostilities
in check please and read what all of us have been saying to you. It seems
that perhaps you DO need some lessons in ASP.NET because we're all telling
you the same thing and you don't seem to be getting what we are trying to
say.

..NET has absolutely NOTHING to do with client-side code that you've embedded
into your page (HTML or JavaScript). Now, if you are embedding your code
into SERVER tags or what you've added CONFLICTS with SERVER tags, you'll
have a problem. There's no bug. ASP.NET has been out for nearly 3 years
now (longer if you include the beta period). It is more likely that you
haven't yet fully learned how ASP.NET pages render their results.

A .NET page, generated by VS.NET will automatically create a SERVER SIDE
<Form> tag. If you've also added your own client-side <Form> tag, you've
got to make sure that is kept separate from the server-side form tag.

The bottom line is that if you simply view the code that was delivered to
the client (by choosing View...Source from the rendered page in the
browser), you can clearly see what .NET has rendered. If what you see there
is not what you started with, then you've entered your code inappropriately
in the first place (probably in the wrong area).
"amos" <so**@caramail.com> wrote in message
news:dd**************************@posting.google.c om...
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.

Nov 18 '05 #14

P: n/a
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" <so**@caramail.com> a écrit dans le message de
news:dd**************************@posting.google.c om...
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" <no****@nowhere.com> wrote in message

news:<uw**************@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" <so**@caramail.com> a écrit dans le message de
news:dd**************************@posting.google.c om...
The source is SIMILAR

..

that's why the question remains .. unsolved

"Patrice" <no****@nowhere.com> wrote in message

news:<eJ**************@TK2MSFTNGP14.phx.gbl>...
> Just check the source client side ("view source" or similar) to see if
it's
> different.
>
> Let us know.
>
> Patrice
>
>
> --
>
> "amos" <so**@caramail.com> a écrit dans le message de
> news:dd**************************@posting.google.c om...
> > 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.

Nov 18 '05 #15

P: n/a
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/de...ionsection.asp

Hope it helps.

Patrice

--

"Patrice" <no****@nowhere.com> a écrit dans le message de
news:ev**************@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" <so**@caramail.com> a écrit dans le message de
news:dd**************************@posting.google.c om...
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" <no****@nowhere.com> wrote in message news:<uw**************@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" <so**@caramail.com> a écrit dans le message de
news:dd**************************@posting.google.c om...
> The source is SIMILAR
>
> ..
>
> that's why the question remains .. unsolved
>
> "Patrice" <no****@nowhere.com> wrote in message
news:<eJ**************@TK2MSFTNGP14.phx.gbl>...
> > Just check the source client side ("view source" or similar) to
see
if it's
> > different.
> >
> > Let us know.
> >
> > Patrice
> >
> >
> > --
> >
> > "amos" <so**@caramail.com> a écrit dans le message de
> > news:dd**************************@posting.google.c om...
> > > 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.


Nov 18 '05 #16

P: n/a
Sorry if you think I'm rude, it's just I asked a for an answer to the
question, not for any proverb. There is no hostility.

Concerning the problem, I just have to say that we don't understand
each other.

I tell you that the code in the navigator IS THE SAME
that the one I entered. And in the ASPX page it does not work
(when it works in a HTML or ASP page for example).

And I paste the javascript code in the HTML <HEAD> section,
it's not in a server object.

All other Javascript code I write works on all the navigators.

So that's why I insist on this point, there must be a bug somewhere
in the DotNet section.

When you use the instruction doucument.layername.write,
it makes strange caracters appearing on the screen.

You can only see this in NETSCAPE4 since it's the only known
browser that displays LAYERS.

Am I Clear enough ?


"Scott M." <No****@NoSpam.com> wrote in message news:<ea*************@TK2MSFTNGP11.phx.gbl>...
There is no reason for you to be rude.

My response to your post had nothing to do with ego, so put your hostilities
in check please and read what all of us have been saying to you. It seems
that perhaps you DO need some lessons in ASP.NET because we're all telling
you the same thing and you don't seem to be getting what we are trying to
say.

.NET has absolutely NOTHING to do with client-side code that you've embedded
into your page (HTML or JavaScript). Now, if you are embedding your code
into SERVER tags or what you've added CONFLICTS with SERVER tags, you'll
have a problem. There's no bug. ASP.NET has been out for nearly 3 years
now (longer if you include the beta period). It is more likely that you
haven't yet fully learned how ASP.NET pages render their results.

A .NET page, generated by VS.NET will automatically create a SERVER SIDE
<Form> tag. If you've also added your own client-side <Form> tag, you've
got to make sure that is kept separate from the server-side form tag.

The bottom line is that if you simply view the code that was delivered to
the client (by choosing View...Source from the rendered page in the
browser), you can clearly see what .NET has rendered. If what you see there
is not what you started with, then you've entered your code inappropriately
in the first place (probably in the wrong area).
"amos" <so**@caramail.com> wrote in message
news:dd**************************@posting.google.c om...
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.

Nov 18 '05 #17

P: n/a
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" <no****@nowhere.com> wrote in message news:<e8**************@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/de...ionsection.asp

Hope it helps.

Patrice

--

"Patrice" <no****@nowhere.com> a écrit dans le message de
news:ev**************@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" <so**@caramail.com> a écrit dans le message de
news:dd**************************@posting.google.c om...
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" <no****@nowhere.com> wrote in message news:<uw**************@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" <so**@caramail.com> a écrit dans le message de
> news:dd**************************@posting.google.c om...
> > The source is SIMILAR
> >
> > ..
> >
> > that's why the question remains .. unsolved
> >
> > "Patrice" <no****@nowhere.com> wrote in message news:<eJ**************@TK2MSFTNGP14.phx.gbl>... > > > Just check the source client side ("view source" or similar) to see
if
it's > > > different.
> > >
> > > Let us know.
> > >
> > > Patrice
> > >
> > >
> > > --
> > >
> > > "amos" <so**@caramail.com> a écrit dans le message de
> > > news:dd**************************@posting.google.c om...
> > > > 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.


Nov 18 '05 #18

P: n/a
Hi Ken

You can't test it on Netscape 7 since the only browser that
accepts LAYERS is Netscape 4...

"Ken Dopierala Jr." <kd*********@wi.rr.com> wrote in message news:<uM**************@TK2MSFTNGP10.phx.gbl>...
Hi,

I gave the code you posted a spin. I don't have Netscape 4.? (there are
about 17 versions of 4 if you include the betas). I do have Netscape 7.1
and your code didn't work in that as a .html or a .aspx file. Can you test
on 7.1 if your code works for you. If it does please repost the entire code
page you are using. The code you posted before has two forms in it, no
<HTML> tag, no <HEAD> tag and no <BODY> tag, so who knows what is all going
on in your page. Just post the entire .html file you are using from the
first line to the last and we'll see if we can figure something out. I have
a pretty good idea that this has nothing to do with ASP.Net and everything
to do with Netscape 4. In your last reply to Patrice you felt that when
hitting an ASPX page the .write method of iLayer was writing to Netscape
memory. I highly doubt this, but if it is the case then we should figure it
out before someone actually learns how to use it to take over any
unsuspecting Netscape 4 users out there. Good luck! Ken.

--
Ken Dopierala Jr.
For great ASP.Net web hosting try:
http://www.webhost4life.com/default.asp?refid=Spinlight

"amos" <so**@caramail.com> wrote in message
news:dd**************************@posting.google.c om...
No, I only have one form ..

THe problem does not come from the source that works properly, it
comes from an interference from netscape4 & dotnet ..

For example, another point that is strange, when you make a
Response.redirect, in Netscape 4, sometimes, the navigator put a blank
page with a link which is (THE PAGE HAS MOVED HERE) and when you click
on the link, you go to the page that has been redirected.. but this is
not the problem that I want to fix today
"TJS" <no****@here.com> wrote in message

news:<#p**************@TK2MSFTNGP10.phx.gbl>...
I think it does not work because you have two forms in your html. In aspx, pages are treated as postback and only use 1 form.
"amos" <so**@caramail.com> wrote in message
news:dd**************************@posting.google.c om...
> Hi
>
> I'm experiencing a real nasty thing about dotnet.
>
> I've made a big application in dotnet and I would like
> to use ILAYERS for netscape 4.
>
> You CAN NOT USE Layers and Form buttons in Netscape 4
> if you save your page in .aspx
>
> Try to save the following code in .html and in .aspx
> then look at those two pages in Netscape 4 :
>
> <script language=javascript>
> function ChangeIntitule()
> {
> if (document.Form1.Origine.selectedIndex==0)
> stringX="";
> if (document.Form1.Origine.selectedIndex==1)
> stringX="Exemple: '1992-1998 : Ecole supérieure d'art dramatique de Paris'"; > if (document.Form1.Origine.selectedIndex==2)
> stringX="Exemple: '2002 : Sara Pearson, Patrik Widrig (Contact Improvisation)'"; > if (document.Form1.Origine.selectedIndex==3)
> stringX="Exemple: '2003 : Cinéma - Film Snatch - figuration 3 jours'";
> if (document.Form1.Origine.selectedIndex==4)
> stringX="Exemple: 'Mime', 'Pianiste', 'Trapeziste', etc..";
> if (document.Form1.Origine.selectedIndex==5)
> stringX="Exemple: 'yoga', 'photographie', 'sculpture', etc..";
>
> if (document.layers){
>
> document.countdownnsmain.document.countdownnssub.d ocument.write(stringX); > document.countdownnsmain.document.countdownnssub.d ocument.close();
> }
> else if (document.all||document.getElementById)
> crosscount.innerHTML=stringX;
> }
> </script>
>
> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> > <form name=Form1>
> <select name="Origine" id="Origine" class="letras" onchange="ChangeIntitule();"> > <option value="-1">Choisissez une rubrique</option>
> <option value="0">Etudes / Formation Artistique</option>
> <option value="1">Stage / Séminaire</option>
> <option value="2">Expérience professionnelle</option>
> <option value="3">Activité Artistique</option>
> <option value="4">Loisirs</option>
>
> </select><input type=text name=sqdf>
> </form>
> <form name=qsd>
> <ilayer id="countdownnsmain" width=300; height=50; visibility=show>
> <layer id="countdownnssub" width=300; height=50; left=0 top=0> </layer> > </ilayer>
> </form>
>
>
> You'll see that all the codes that you wrote for Netscape4 whith
> the ILAYERS don't work if you save the page as .aspx.
>
>
> IS THIS A HUGE BUG OF DOT NET ????????

Nov 18 '05 #19

P: n/a
Hi,

That's fine. But post your files. First post the .HTML file you are using
from the first line to the last. Then post your .aspx page from the first
line to the last. Then post your .aspx.vb page from the first line to the
last. I want to run them and see if they both produce the same output. The
problem isn't with ASP.Net, just to put your mind at rest. You have a
scripting problem. Once you find it, you'll be good to go. Post the pages
and we'll find the problem. Good luck! Ken.

--
Ken Dopierala Jr.
For great ASP.Net web hosting try:
http://www.webhost4life.com/default.asp?refid=Spinlight

"amos" <so**@caramail.com> wrote in message
news:dd**************************@posting.google.c om...
Hi Ken

You can't test it on Netscape 7 since the only browser that
accepts LAYERS is Netscape 4...

"Ken Dopierala Jr." <kd*********@wi.rr.com> wrote in message

news:<uM**************@TK2MSFTNGP10.phx.gbl>...
Hi,

I gave the code you posted a spin. I don't have Netscape 4.? (there are
about 17 versions of 4 if you include the betas). I do have Netscape 7.1 and your code didn't work in that as a .html or a .aspx file. Can you test on 7.1 if your code works for you. If it does please repost the entire code page you are using. The code you posted before has two forms in it, no
<HTML> tag, no <HEAD> tag and no <BODY> tag, so who knows what is all going on in your page. Just post the entire .html file you are using from the
first line to the last and we'll see if we can figure something out. I have a pretty good idea that this has nothing to do with ASP.Net and everything to do with Netscape 4. In your last reply to Patrice you felt that when
hitting an ASPX page the .write method of iLayer was writing to Netscape
memory. I highly doubt this, but if it is the case then we should figure it out before someone actually learns how to use it to take over any
unsuspecting Netscape 4 users out there. Good luck! Ken.

--
Ken Dopierala Jr.
For great ASP.Net web hosting try:
http://www.webhost4life.com/default.asp?refid=Spinlight

"amos" <so**@caramail.com> wrote in message
news:dd**************************@posting.google.c om...
No, I only have one form ..

THe problem does not come from the source that works properly, it
comes from an interference from netscape4 & dotnet ..

For example, another point that is strange, when you make a
Response.redirect, in Netscape 4, sometimes, the navigator put a blank
page with a link which is (THE PAGE HAS MOVED HERE) and when you click
on the link, you go to the page that has been redirected.. but this is
not the problem that I want to fix today
"TJS" <no****@here.com> wrote in message

news:<#p**************@TK2MSFTNGP10.phx.gbl>...
> I think it does not work because you have two forms in your html. In
aspx,
> pages are treated as postback and only use 1 form.
>
>
> "amos" <so**@caramail.com> wrote in message
> news:dd**************************@posting.google.c om...
> > Hi
> >
> > I'm experiencing a real nasty thing about dotnet.
> >
> > I've made a big application in dotnet and I would like
> > to use ILAYERS for netscape 4.
> >
> > You CAN NOT USE Layers and Form buttons in Netscape 4
> > if you save your page in .aspx
> >
> > Try to save the following code in .html and in .aspx
> > then look at those two pages in Netscape 4 :
> >
> > <script language=javascript>
> > function ChangeIntitule()
> > {
> > if (document.Form1.Origine.selectedIndex==0)
> > stringX="";
> > if (document.Form1.Origine.selectedIndex==1)
> > stringX="Exemple: '1992-1998 : Ecole supérieure d'art dramatique
de Paris'";
> > if (document.Form1.Origine.selectedIndex==2)
> > stringX="Exemple: '2002 : Sara Pearson, Patrik Widrig (Contact

Improvisation)'";
> > if (document.Form1.Origine.selectedIndex==3)
> > stringX="Exemple: '2003 : Cinéma - Film Snatch - figuration 3

jours'"; > > if (document.Form1.Origine.selectedIndex==4)
> > stringX="Exemple: 'Mime', 'Pianiste', 'Trapeziste', etc..";
> > if (document.Form1.Origine.selectedIndex==5)
> > stringX="Exemple: 'yoga', 'photographie', 'sculpture', etc..";
> >
> > if (document.layers){
> >
> >

document.countdownnsmain.document.countdownnssub.d ocument.write(stringX);
> > document.countdownnsmain.document.countdownnssub.d ocument.close();
> > }
> > else if (document.all||document.getElementById)
> > crosscount.innerHTML=stringX;
> > }
> > </script>
> >
> > <meta http-equiv="Content-Type" content="text/html;

charset=iso-8859-1">
> > <form name=Form1>
> > <select name="Origine" id="Origine" class="letras"

onchange="ChangeIntitule();">
> > <option value="-1">Choisissez une rubrique</option>
> > <option value="0">Etudes / Formation Artistique</option>
> > <option value="1">Stage / Séminaire</option>
> > <option value="2">Expérience professionnelle</option>
> > <option value="3">Activité Artistique</option>
> > <option value="4">Loisirs</option>
> >
> > </select><input type=text name=sqdf>
> > </form>
> > <form name=qsd>
> > <ilayer id="countdownnsmain" width=300; height=50; visibility=show> > > <layer id="countdownnssub" width=300; height=50; left=0 top=0>

</layer>
> > </ilayer>
> > </form>
> >
> >
> > You'll see that all the codes that you wrote for Netscape4 whith
> > the ILAYERS don't work if you save the page as .aspx.
> >
> >
> > IS THIS A HUGE BUG OF DOT NET ????????

Nov 18 '05 #20

P: n/a
- do you have this problem on accented characters ?
- what if you write directly to the document object ?
- can you give us the character code used instead of the expected characters
?
- can you see the HTTP header of the page in NS4 ?

Patrice

--

"amos" <so**@caramail.com> a écrit dans le message de
news:dd**************************@posting.google.c om...
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" <no****@nowhere.com> wrote in message

news:<e8**************@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/de...ionsection.asp
Hope it helps.

Patrice

--

"Patrice" <no****@nowhere.com> a écrit dans le message de
news:ev**************@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" <so**@caramail.com> a écrit dans le message de
news:dd**************************@posting.google.c om...
> 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" <no****@nowhere.com> wrote in message

news:<uw**************@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" <so**@caramail.com> a écrit dans le message de
> > news:dd**************************@posting.google.c om...
> > > The source is SIMILAR
> > >
> > > ..
> > >
> > > that's why the question remains .. unsolved
> > >
> > > "Patrice" <no****@nowhere.com> wrote in message

news:<eJ**************@TK2MSFTNGP14.phx.gbl>...
> > > > Just check the source client side ("view source" or similar)
to see
if
it's
> > > > different.
> > > >
> > > > Let us know.
> > > >
> > > > Patrice
> > > >
> > > >
> > > > --
> > > >
> > > > "amos" <so**@caramail.com> a écrit dans le message de
> > > > news:dd**************************@posting.google.c om...
> > > > > 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.

Nov 18 '05 #21

P: n/a
Okay I think you're right, I post you the source code so you'll see.

I will post 3 files, the .html file, then the .aspx file and then the
..aspx.cs
----------------------------------------------------------------------------
HTML FILE :
----------------------------------------------------------------------------
<html>
<head>

<script language=javascript>
function ChangeIntitule()
{
if (document.Form1.Origine.selectedIndex==0)
stringX="";
if (document.Form1.Origine.selectedIndex==1)
stringX="Exemple: '1992-1998 : Ecole supérieure d'art dramatique de
Paris'";
if (document.Form1.Origine.selectedIndex==2)
stringX="Exemple: '2002 : Sara Pearson, Patrik Widrig (Contact
Improvisation)'";
if (document.Form1.Origine.selectedIndex==3)
stringX="Exemple: '2003 : Cinéma - Film Snatch - figuration 3
jours'";
if (document.Form1.Origine.selectedIndex==4)
stringX="Exemple: 'Mime', 'Pianiste', 'Trapeziste', etc..";
if (document.Form1.Origine.selectedIndex==5)
stringX="Exemple: 'yoga', 'photographie', 'sculpture', etc..";

if (document.layers){

document.countdownnsmain.document.countdownnssub.d ocument.write(stringX);
document.countdownnsmain.document.countdownnssub.d ocument.close();
}
else if (document.all||document.getElementById)
crosscount.innerHTML=stringX;
}
</script>

</head>

<body>
<form name=Form1>
<select name="Origine" id="Origine" class="letras"
onchange="ChangeIntitule();">
<option value="-1">Choisissez une rubrique</option>
<option value="0">Etudes / Formation Artistique</option>
<option value="1">Stage / Séminaire</option>
<option value="2">Expérience professionnelle</option>
<option value="3">Activité Artistique</option>
<option value="4">Loisirs</option>

</select>
</form>
<form name=qsd>
<ilayer id="countdownnsmain" width=300; height=50; visibility=show>
<layer id="countdownnssub" width=300; height=50; left=0 top=0>
</layer>
</ilayer>
</form>

</body>

</html>

----------------------------------------------------------------------------
END OF HTML FILE
----------------------------------------------------------------------------


----------------------------------------------------------------------------
..ASPX FILE (HTML VIEW)
----------------------------------------------------------------------------

<%@ Page language="c#" Codebehind="WebForm1.aspx.cs"
AutoEventWireup="false" Inherits="ProjectTest.WebForm1" %>
<html>
<head>

<script language=javascript>
function ChangeIntitule()
{
if (document.Form1.Origine.selectedIndex==0)
stringX="";
if (document.Form1.Origine.selectedIndex==1)
stringX="Exemple: '1992-1998 : Ecole supérieure d'art dramatique de
Paris'";
if (document.Form1.Origine.selectedIndex==2)
stringX="Exemple: '2002 : Sara Pearson, Patrik Widrig (Contact
Improvisation)'";
if (document.Form1.Origine.selectedIndex==3)
stringX="Exemple: '2003 : Cinéma - Film Snatch - figuration 3
jours'";
if (document.Form1.Origine.selectedIndex==4)
stringX="Exemple: 'Mime', 'Pianiste', 'Trapeziste', etc..";
if (document.Form1.Origine.selectedIndex==5)
stringX="Exemple: 'yoga', 'photographie', 'sculpture', etc..";

if (document.layers){

document.countdownnsmain.document.countdownnssub.d ocument.write(stringX);
document.countdownnsmain.document.countdownnssub.d ocument.close();
}
else if (document.all||document.getElementById)
crosscount.innerHTML=stringX;
}
</script>

</head>

<body>
<form name=Form1>
<select name="Origine" id="Origine" class="letras"
onchange="ChangeIntitule();">
<option value="-1">Choisissez une rubrique</option>
<option value="0">Etudes / Formation Artistique</option>
<option value="1">Stage / Séminaire</option>
<option value="2">Expérience professionnelle</option>
<option value="3">Activité Artistique</option>
<option value="4">Loisirs</option>

</select>
</form>
<form name=qsd>
<ilayer id="countdownnsmain" width=300; height=50; visibility=show>
<layer id="countdownnssub" width=300; height=50; left=0 top=0>
</layer>
</ilayer>
</form>

</body>

</html>

----------------------------------------------------------------------------
END OF .ASPX FILE (HTML VIEW)
----------------------------------------------------------------------------

----------------------------------------------------------------------------
..ASPX.CS FILE
----------------------------------------------------------------------------
using System;
using System.Collections;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Web;
using System.Web.SessionState;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.HtmlControls;
using System.Drawing.Imaging;
using System.Drawing.Drawing2D;


namespace ProjectTest
{
public class WebForm1 : System.Web.UI.Page
{

private void Page_Load(object sender, System.EventArgs e)
{
}

#region Code généré par le Concepteur Web Form
override protected void OnInit(EventArgs e)
{
InitializeComponent();
base.OnInit(e);
}

private void InitializeComponent()
{
this.Load += new System.EventHandler(this.Page_Load);

}
#endregion
}
}
----------------------------------------------------------------------------
END OF .ASPX.CS FILE
----------------------------------------------------------------------------
So check the .HTML render and .ASPX render in Netscape 4 (or any
browser
that accepts LAYERS and you'll see some amazing stuff.
And by the way, thank you for the time you spend on my problem.


"Ken Dopierala Jr." <kd*********@wi.rr.com> wrote in message news:<eQ*************@TK2MSFTNGP15.phx.gbl>...
Hi,

That's fine. But post your files. First post the .HTML file you are using
from the first line to the last. Then post your .aspx page from the first
line to the last. Then post your .aspx.vb page from the first line to the
last. I want to run them and see if they both produce the same output. The
problem isn't with ASP.Net, just to put your mind at rest. You have a
scripting problem. Once you find it, you'll be good to go. Post the pages
and we'll find the problem. Good luck! Ken.

--
Ken Dopierala Jr.
For great ASP.Net web hosting try:
http://www.webhost4life.com/default.asp?refid=Spinlight

"amos" <so**@caramail.com> wrote in message
news:dd**************************@posting.google.c om...
Hi Ken

You can't test it on Netscape 7 since the only browser that
accepts LAYERS is Netscape 4...

"Ken Dopierala Jr." <kd*********@wi.rr.com> wrote in message

news:<uM**************@TK2MSFTNGP10.phx.gbl>...
Hi,

I gave the code you posted a spin. I don't have Netscape 4.? (there are about 17 versions of 4 if you include the betas). I do have Netscape 7.1 and your code didn't work in that as a .html or a .aspx file. Can you test on 7.1 if your code works for you. If it does please repost the entire code page you are using. The code you posted before has two forms in it, no
<HTML> tag, no <HEAD> tag and no <BODY> tag, so who knows what is all going on in your page. Just post the entire .html file you are using from the
first line to the last and we'll see if we can figure something out. I have a pretty good idea that this has nothing to do with ASP.Net and everything to do with Netscape 4. In your last reply to Patrice you felt that when
hitting an ASPX page the .write method of iLayer was writing to Netscape
memory. I highly doubt this, but if it is the case then we should figure it out before someone actually learns how to use it to take over any
unsuspecting Netscape 4 users out there. Good luck! Ken.

--
Ken Dopierala Jr.
For great ASP.Net web hosting try:
http://www.webhost4life.com/default.asp?refid=Spinlight

"amos" <so**@caramail.com> wrote in message
news:dd**************************@posting.google.c om...
> No, I only have one form ..
>
> THe problem does not come from the source that works properly, it
> comes from an interference from netscape4 & dotnet ..
>
> For example, another point that is strange, when you make a
> Response.redirect, in Netscape 4, sometimes, the navigator put a blank
> page with a link which is (THE PAGE HAS MOVED HERE) and when you click
> on the link, you go to the page that has been redirected.. but this is
> not the problem that I want to fix today
>
>
> "TJS" <no****@here.com> wrote in message news:<#p**************@TK2MSFTNGP10.phx.gbl>... > > I think it does not work because you have two forms in your html. In
aspx, > > pages are treated as postback and only use 1 form.
> >
> >
> > "amos" <so**@caramail.com> wrote in message
> > news:dd**************************@posting.google.c om...
> > > Hi
> > >
> > > I'm experiencing a real nasty thing about dotnet.
> > >
> > > I've made a big application in dotnet and I would like
> > > to use ILAYERS for netscape 4.
> > >
> > > You CAN NOT USE Layers and Form buttons in Netscape 4
> > > if you save your page in .aspx
> > >
> > > Try to save the following code in .html and in .aspx
> > > then look at those two pages in Netscape 4 :
> > >
> > > <script language=javascript>
> > > function ChangeIntitule()
> > > {
> > > if (document.Form1.Origine.selectedIndex==0)
> > > stringX="";
> > > if (document.Form1.Origine.selectedIndex==1)
> > > stringX="Exemple: '1992-1998 : Ecole supérieure d'art dramatique de
Paris'"; > > > if (document.Form1.Origine.selectedIndex==2)
> > > stringX="Exemple: '2002 : Sara Pearson, Patrik Widrig (Contact Improvisation)'"; > > > if (document.Form1.Origine.selectedIndex==3)
> > > stringX="Exemple: '2003 : Cinéma - Film Snatch - figuration 3 jours'"; > > > if (document.Form1.Origine.selectedIndex==4)
> > > stringX="Exemple: 'Mime', 'Pianiste', 'Trapeziste', etc..";
> > > if (document.Form1.Origine.selectedIndex==5)
> > > stringX="Exemple: 'yoga', 'photographie', 'sculpture', etc..";
> > >
> > > if (document.layers){
> > >
> > >
document.countdownnsmain.document.countdownnssub.d ocument.write(stringX); > > > document.countdownnsmain.document.countdownnssub.d ocument.close();
> > > }
> > > else if (document.all||document.getElementById)
> > > crosscount.innerHTML=stringX;
> > > }
> > > </script>
> > >
> > > <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> > > > <form name=Form1>
> > > <select name="Origine" id="Origine" class="letras" onchange="ChangeIntitule();"> > > > <option value="-1">Choisissez une rubrique</option>
> > > <option value="0">Etudes / Formation Artistique</option>
> > > <option value="1">Stage / Séminaire</option>
> > > <option value="2">Expérience professionnelle</option>
> > > <option value="3">Activité Artistique</option>
> > > <option value="4">Loisirs</option>
> > >
> > > </select><input type=text name=sqdf>
> > > </form>
> > > <form name=qsd>
> > > <ilayer id="countdownnsmain" width=300; height=50; visibility=show> > > > <layer id="countdownnssub" width=300; height=50; left=0 top=0> </layer> > > > </ilayer>
> > > </form>
> > >
> > >
> > > You'll see that all the codes that you wrote for Netscape4 whith
> > > the ILAYERS don't work if you save the page as .aspx.
> > >
> > >
> > > IS THIS A HUGE BUG OF DOT NET ????????

Nov 18 '05 #22

P: n/a
I will post 3 files, the .html file, then the .aspx file and then the
..aspx.cs so you'll see by yourself where the bug comes from.
----------------------------------------------------------------------------
HTML FILE :
----------------------------------------------------------------------------
<html>
<head>

<script language=javascript>
function ChangeIntitule()
{
if (document.Form1.Origine.selectedIndex==0)
stringX="";
if (document.Form1.Origine.selectedIndex==1)
stringX="Exemple: '1992-1998 : Ecole supérieure d'art dramatique de
Paris'";
if (document.Form1.Origine.selectedIndex==2)
stringX="Exemple: '2002 : Sara Pearson, Patrik Widrig (Contact
Improvisation)'";
if (document.Form1.Origine.selectedIndex==3)
stringX="Exemple: '2003 : Cinéma - Film Snatch - figuration 3
jours'";
if (document.Form1.Origine.selectedIndex==4)
stringX="Exemple: 'Mime', 'Pianiste', 'Trapeziste', etc..";
if (document.Form1.Origine.selectedIndex==5)
stringX="Exemple: 'yoga', 'photographie', 'sculpture', etc..";

if (document.layers){

document.countdownnsmain.document.countdownnssub.d ocument.write(stringX);
document.countdownnsmain.document.countdownnssub.d ocument.close();
}
else if (document.all||document.getElementById)
crosscount.innerHTML=stringX;
}
</script>

</head>

<body>
<form name=Form1>
<select name="Origine" id="Origine" class="letras"
onchange="ChangeIntitule();">
<option value="-1">Choisissez une rubrique</option>
<option value="0">Etudes / Formation Artistique</option>
<option value="1">Stage / Séminaire</option>
<option value="2">Expérience professionnelle</option>
<option value="3">Activité Artistique</option>
<option value="4">Loisirs</option>

</select>
</form>
<form name=qsd>
<ilayer id="countdownnsmain" width=300; height=50; visibility=show>
<layer id="countdownnssub" width=300; height=50; left=0 top=0>
</layer>
</ilayer>
</form>

</body>

</html>

----------------------------------------------------------------------------
END OF HTML FILE
----------------------------------------------------------------------------


----------------------------------------------------------------------------
..ASPX FILE (HTML VIEW)
----------------------------------------------------------------------------

<%@ Page language="c#" Codebehind="WebForm1.aspx.cs"
AutoEventWireup="false" Inherits="ProjectTest.WebForm1" %>
<html>
<head>

<script language=javascript>
function ChangeIntitule()
{
if (document.Form1.Origine.selectedIndex==0)
stringX="";
if (document.Form1.Origine.selectedIndex==1)
stringX="Exemple: '1992-1998 : Ecole supérieure d'art dramatique de
Paris'";
if (document.Form1.Origine.selectedIndex==2)
stringX="Exemple: '2002 : Sara Pearson, Patrik Widrig (Contact
Improvisation)'";
if (document.Form1.Origine.selectedIndex==3)
stringX="Exemple: '2003 : Cinéma - Film Snatch - figuration 3
jours'";
if (document.Form1.Origine.selectedIndex==4)
stringX="Exemple: 'Mime', 'Pianiste', 'Trapeziste', etc..";
if (document.Form1.Origine.selectedIndex==5)
stringX="Exemple: 'yoga', 'photographie', 'sculpture', etc..";

if (document.layers){

document.countdownnsmain.document.countdownnssub.d ocument.write(stringX);
document.countdownnsmain.document.countdownnssub.d ocument.close();
}
else if (document.all||document.getElementById)
crosscount.innerHTML=stringX;
}
</script>

</head>

<body>
<form name=Form1>
<select name="Origine" id="Origine" class="letras"
onchange="ChangeIntitule();">
<option value="-1">Choisissez une rubrique</option>
<option value="0">Etudes / Formation Artistique</option>
<option value="1">Stage / Séminaire</option>
<option value="2">Expérience professionnelle</option>
<option value="3">Activité Artistique</option>
<option value="4">Loisirs</option>

</select>
</form>
<form name=qsd>
<ilayer id="countdownnsmain" width=300; height=50; visibility=show>
<layer id="countdownnssub" width=300; height=50; left=0 top=0>
</layer>
</ilayer>
</form>

</body>

</html>

----------------------------------------------------------------------------
END OF .ASPX FILE (HTML VIEW)
----------------------------------------------------------------------------

----------------------------------------------------------------------------
..ASPX.CS FILE
----------------------------------------------------------------------------
using System;
using System.Collections;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Web;
using System.Web.SessionState;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.HtmlControls;
using System.Drawing.Imaging;
using System.Drawing.Drawing2D;


namespace ProjectTest
{
public class WebForm1 : System.Web.UI.Page
{

private void Page_Load(object sender, System.EventArgs e)
{
}

#region Code généré par le Concepteur Web Form
override protected void OnInit(EventArgs e)
{
InitializeComponent();
base.OnInit(e);
}

private void InitializeComponent()
{
this.Load += new System.EventHandler(this.Page_Load);

} #endregion
}
}
----------------------------------------------------------------------------
END OF .ASPX.CS FILE
----------------------------------------------------------------------------
So check the .HTML render and .ASPX render in Netscape 4 (or any
browser
that accepts LAYERS and you'll see some amazing stuff.
And by the way, thank you for the time you spend on my problem.



"Patrice" <no****@nowhere.com> wrote in message news:<ej**************@TK2MSFTNGP14.phx.gbl>...
- do you have this problem on accented characters ?
- what if you write directly to the document object ?
- can you give us the character code used instead of the expected characters
?
- can you see the HTTP header of the page in NS4 ?

Patrice

--

"amos" <so**@caramail.com> a écrit dans le message de
news:dd**************************@posting.google.c om...
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" <no****@nowhere.com> wrote in message

news:<e8**************@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/de...ionsection.asp
Hope it helps.

Patrice

--

"Patrice" <no****@nowhere.com> a écrit dans le message de
news:ev**************@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" <so**@caramail.com> a écrit dans le message de
> news:dd**************************@posting.google.c om...
> > 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" <no****@nowhere.com> wrote in message news:<uw**************@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" <so**@caramail.com> a écrit dans le message de
> > > news:dd**************************@posting.google.c om...
> > > > The source is SIMILAR
> > > >
> > > > ..
> > > >
> > > > that's why the question remains .. unsolved
> > > >
> > > > "Patrice" <no****@nowhere.com> wrote in message news:<eJ**************@TK2MSFTNGP14.phx.gbl>... > > > > > Just check the source client side ("view source" or similar) to see
if
it's
> > > > > different.
> > > > >
> > > > > Let us know.
> > > > >
> > > > > Patrice
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > "amos" <so**@caramail.com> a écrit dans le message de
> > > > > news:dd**************************@posting.google.c om...
> > > > > > 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.
>
>

Nov 18 '05 #23

P: n/a
Hi,

I took a look at this. I couldn't test it on Netscape 4 because the only
version I could find to download was 4.78 and it wouldn't install on Windows
2000. But I have a few suggestions. First of all the HTML that is rendered
is different. ASP.Net doesn't support using two forms. So what happens is
that in your HTML rendered page it adds an id attribute: id="Form1" and
id="Form2", when the .ASPX page renders it doesn't add those. This could be
what is allowing the javascript engine in Netscape 4 to be able to access
the layer stuff in the HTML page and not the ASPX page.

What I suggest you try is to inject your 2nd form into the page when the
page renders. You do this by overriding the Render method of the page.
This is in VB but to move it to C# about all you should have to change is
the function declaration and the variable declarations. Remember to include
the System.IO and System.Text namespaces.

Protected Overrides Sub Render(ByVal writer As
System.Web.UI.HtmlTextWriter)
Dim sw As StringWriter
Dim htmltw As HtmlTextWriter
Dim strText As String
'Assign the html to strText here.
sw = New StringWriter()
htmltw = New HtmlTextWriter(sw)
MyBase.Render(htmltw)
Dim temp As StringBuilder
temp = sw.GetStringBuilder
Dim str As String
str = temp.ToString
str = str.Replace("</form>", "</form> " + strText)
writer.Write(str)
End Sub

Set strText equal to the code below (don't forget to include the form ID and
make sure your quotes are correct):

<form name='qsd' id='Form2'>
<ilayer id="countdownnsmain" width=300; height=50; visibility=show>
<layer id="countdownnssub" width=300; height=50; left=0 top=0>
</layer>
</ilayer>
</form>

And remove that form from your ASPX page. This might get it working for you
but no guarantees. Also in your ilayer and layer tags make sure they are
formated properly. In some places you use ';' others you don't, around one
attribute you have quotes and others you don't. Anyway, that's how I would
approach making this work. Since I can't actually test this I can't tell
you how it will play out, but even if it doesn't work 100% keep your eyes
open for small things that might point you in the right direction. Good
luck! Ken.

--
Ken Dopierala Jr.
For great ASP.Net web hosting try:
http://www.webhost4life.com/default.asp?refid=Spinlight
If you sign up under me and need help, email me.
Nov 18 '05 #24

P: n/a
Hello

try changing this in web.config the globalization setting in web.config to
look like this
<globalization requestEncoding="windows-1252"
responseEncoding="windows-1252" fileEncoding="windows-1252" />

Best regards,
Sherif

"amos" wrote:
Sorry if you think I'm rude, it's just I asked a for an answer to the
question, not for any proverb. There is no hostility.

Concerning the problem, I just have to say that we don't understand
each other.

I tell you that the code in the navigator IS THE SAME
that the one I entered. And in the ASPX page it does not work
(when it works in a HTML or ASP page for example).

And I paste the javascript code in the HTML <HEAD> section,
it's not in a server object.

All other Javascript code I write works on all the navigators.

So that's why I insist on this point, there must be a bug somewhere
in the DotNet section.

When you use the instruction doucument.layername.write,
it makes strange caracters appearing on the screen.

You can only see this in NETSCAPE4 since it's the only known
browser that displays LAYERS.

Am I Clear enough ?


"Scott M." <No****@NoSpam.com> wrote in message news:<ea*************@TK2MSFTNGP11.phx.gbl>...
There is no reason for you to be rude.

My response to your post had nothing to do with ego, so put your hostilities
in check please and read what all of us have been saying to you. It seems
that perhaps you DO need some lessons in ASP.NET because we're all telling
you the same thing and you don't seem to be getting what we are trying to
say.

.NET has absolutely NOTHING to do with client-side code that you've embedded
into your page (HTML or JavaScript). Now, if you are embedding your code
into SERVER tags or what you've added CONFLICTS with SERVER tags, you'll
have a problem. There's no bug. ASP.NET has been out for nearly 3 years
now (longer if you include the beta period). It is more likely that you
haven't yet fully learned how ASP.NET pages render their results.

A .NET page, generated by VS.NET will automatically create a SERVER SIDE
<Form> tag. If you've also added your own client-side <Form> tag, you've
got to make sure that is kept separate from the server-side form tag.

The bottom line is that if you simply view the code that was delivered to
the client (by choosing View...Source from the rendered page in the
browser), you can clearly see what .NET has rendered. If what you see there
is not what you started with, then you've entered your code inappropriately
in the first place (probably in the wrong area).
"amos" <so**@caramail.com> wrote in message
news:dd**************************@posting.google.c om...
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.

Nov 18 '05 #25

P: n/a
Thank you, it solved the problem!!!!!
"Sherif El-Metainy" <Sherif El********@discussions.microsoft.com> wrote in message news:<D8**********************************@microso ft.com>...
Hello

try changing this in web.config the globalization setting in web.config to
look like this
<globalization requestEncoding="windows-1252"
responseEncoding="windows-1252" fileEncoding="windows-1252" />

Best regards,
Sherif

"amos" wrote:
Sorry if you think I'm rude, it's just I asked a for an answer to the
question, not for any proverb. There is no hostility.

Concerning the problem, I just have to say that we don't understand
each other.

I tell you that the code in the navigator IS THE SAME
that the one I entered. And in the ASPX page it does not work
(when it works in a HTML or ASP page for example).

And I paste the javascript code in the HTML <HEAD> section,
it's not in a server object.

All other Javascript code I write works on all the navigators.

So that's why I insist on this point, there must be a bug somewhere
in the DotNet section.

When you use the instruction doucument.layername.write,
it makes strange caracters appearing on the screen.

You can only see this in NETSCAPE4 since it's the only known
browser that displays LAYERS.

Am I Clear enough ?


"Scott M." <No****@NoSpam.com> wrote in message news:<ea*************@TK2MSFTNGP11.phx.gbl>...
There is no reason for you to be rude.

My response to your post had nothing to do with ego, so put your hostilities
in check please and read what all of us have been saying to you. It seems
that perhaps you DO need some lessons in ASP.NET because we're all telling
you the same thing and you don't seem to be getting what we are trying to
say.

.NET has absolutely NOTHING to do with client-side code that you've embedded
into your page (HTML or JavaScript). Now, if you are embedding your code
into SERVER tags or what you've added CONFLICTS with SERVER tags, you'll
have a problem. There's no bug. ASP.NET has been out for nearly 3 years
now (longer if you include the beta period). It is more likely that you
haven't yet fully learned how ASP.NET pages render their results.

A .NET page, generated by VS.NET will automatically create a SERVER SIDE
<Form> tag. If you've also added your own client-side <Form> tag, you've
got to make sure that is kept separate from the server-side form tag.

The bottom line is that if you simply view the code that was delivered to
the client (by choosing View...Source from the rendered page in the
browser), you can clearly see what .NET has rendered. If what you see there
is not what you started with, then you've entered your code inappropriately
in the first place (probably in the wrong area).
"amos" <so**@caramail.com> wrote in message
news:dd**************************@posting.google.c om...
> 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.

Nov 18 '05 #26

P: n/a
The solution comes from sherif !! :

Hello

try changing this in web.config the globalization setting in web.config to
look like this
<globalization requestEncoding="windows-1252"
responseEncoding="windows-1252" fileEncoding="windows-1252" />

Best regards,
Sherif


"Ken Dopierala Jr." <kd*********@wi.rr.com> wrote in message news:<O7**************@TK2MSFTNGP12.phx.gbl>...
Hi,

I took a look at this. I couldn't test it on Netscape 4 because the only
version I could find to download was 4.78 and it wouldn't install on Windows
2000. But I have a few suggestions. First of all the HTML that is rendered
is different. ASP.Net doesn't support using two forms. So what happens is
that in your HTML rendered page it adds an id attribute: id="Form1" and
id="Form2", when the .ASPX page renders it doesn't add those. This could be
what is allowing the javascript engine in Netscape 4 to be able to access
the layer stuff in the HTML page and not the ASPX page.

What I suggest you try is to inject your 2nd form into the page when the
page renders. You do this by overriding the Render method of the page.
This is in VB but to move it to C# about all you should have to change is
the function declaration and the variable declarations. Remember to include
the System.IO and System.Text namespaces.

Protected Overrides Sub Render(ByVal writer As
System.Web.UI.HtmlTextWriter)
Dim sw As StringWriter
Dim htmltw As HtmlTextWriter
Dim strText As String
'Assign the html to strText here.
sw = New StringWriter()
htmltw = New HtmlTextWriter(sw)
MyBase.Render(htmltw)
Dim temp As StringBuilder
temp = sw.GetStringBuilder
Dim str As String
str = temp.ToString
str = str.Replace("</form>", "</form> " + strText)
writer.Write(str)
End Sub

Set strText equal to the code below (don't forget to include the form ID and
make sure your quotes are correct):

<form name='qsd' id='Form2'>
<ilayer id="countdownnsmain" width=300; height=50; visibility=show>
<layer id="countdownnssub" width=300; height=50; left=0 top=0>
</layer>
</ilayer>
</form>

And remove that form from your ASPX page. This might get it working for you
but no guarantees. Also in your ilayer and layer tags make sure they are
formated properly. In some places you use ';' others you don't, around one
attribute you have quotes and others you don't. Anyway, that's how I would
approach making this work. Since I can't actually test this I can't tell
you how it will play out, but even if it doesn't work 100% keep your eyes
open for small things that might point you in the right direction. Good
luck! Ken.

Nov 18 '05 #27

P: n/a
it works great,

just a question, when I change from utf8 to windows-1252,
will it change something for the rest of my app ?

"Sherif El-Metainy" <Sherif El********@discussions.microsoft.com> wrote in message news:<D8**********************************@microso ft.com>...
Hello

try changing this in web.config the globalization setting in web.config to
look like this
<globalization requestEncoding="windows-1252"
responseEncoding="windows-1252" fileEncoding="windows-1252" />

Best regards,
Sherif

"amos" wrote:
Sorry if you think I'm rude, it's just I asked a for an answer to the
question, not for any proverb. There is no hostility.

Concerning the problem, I just have to say that we don't understand
each other.

I tell you that the code in the navigator IS THE SAME
that the one I entered. And in the ASPX page it does not work
(when it works in a HTML or ASP page for example).

And I paste the javascript code in the HTML <HEAD> section,
it's not in a server object.

All other Javascript code I write works on all the navigators.

So that's why I insist on this point, there must be a bug somewhere
in the DotNet section.

When you use the instruction doucument.layername.write,
it makes strange caracters appearing on the screen.

You can only see this in NETSCAPE4 since it's the only known
browser that displays LAYERS.

Am I Clear enough ?


"Scott M." <No****@NoSpam.com> wrote in message news:<ea*************@TK2MSFTNGP11.phx.gbl>...
There is no reason for you to be rude.

My response to your post had nothing to do with ego, so put your hostilities
in check please and read what all of us have been saying to you. It seems
that perhaps you DO need some lessons in ASP.NET because we're all telling
you the same thing and you don't seem to be getting what we are trying to
say.

.NET has absolutely NOTHING to do with client-side code that you've embedded
into your page (HTML or JavaScript). Now, if you are embedding your code
into SERVER tags or what you've added CONFLICTS with SERVER tags, you'll
have a problem. There's no bug. ASP.NET has been out for nearly 3 years
now (longer if you include the beta period). It is more likely that you
haven't yet fully learned how ASP.NET pages render their results.

A .NET page, generated by VS.NET will automatically create a SERVER SIDE
<Form> tag. If you've also added your own client-side <Form> tag, you've
got to make sure that is kept separate from the server-side form tag.

The bottom line is that if you simply view the code that was delivered to
the client (by choosing View...Source from the rendered page in the
browser), you can clearly see what .NET has rendered. If what you see there
is not what you started with, then you've entered your code inappropriately
in the first place (probably in the wrong area).
"amos" <so**@caramail.com> wrote in message
news:dd**************************@posting.google.c om...
> 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.

Nov 18 '05 #28

P: n/a
Hey, congratulations!

I actually thought you tried that already and it didn't work. Patrice told
you back on the 29th to do that. Glad it is working for you! Ken.

"amos" <so**@caramail.com> wrote in message
news:dd**************************@posting.google.c om...
The solution comes from sherif !! :

Hello

try changing this in web.config the globalization setting in web.config to
look like this
<globalization requestEncoding="windows-1252"
responseEncoding="windows-1252" fileEncoding="windows-1252" />

Best regards,
Sherif


"Ken Dopierala Jr." <kd*********@wi.rr.com> wrote in message

news:<O7**************@TK2MSFTNGP12.phx.gbl>...
Hi,

I took a look at this. I couldn't test it on Netscape 4 because the only version I could find to download was 4.78 and it wouldn't install on Windows 2000. But I have a few suggestions. First of all the HTML that is rendered is different. ASP.Net doesn't support using two forms. So what happens is that in your HTML rendered page it adds an id attribute: id="Form1" and
id="Form2", when the .ASPX page renders it doesn't add those. This could be what is allowing the javascript engine in Netscape 4 to be able to access the layer stuff in the HTML page and not the ASPX page.

What I suggest you try is to inject your 2nd form into the page when the
page renders. You do this by overriding the Render method of the page.
This is in VB but to move it to C# about all you should have to change is the function declaration and the variable declarations. Remember to include the System.IO and System.Text namespaces.

Protected Overrides Sub Render(ByVal writer As
System.Web.UI.HtmlTextWriter)
Dim sw As StringWriter
Dim htmltw As HtmlTextWriter
Dim strText As String
'Assign the html to strText here.
sw = New StringWriter()
htmltw = New HtmlTextWriter(sw)
MyBase.Render(htmltw)
Dim temp As StringBuilder
temp = sw.GetStringBuilder
Dim str As String
str = temp.ToString
str = str.Replace("</form>", "</form> " + strText)
writer.Write(str)
End Sub

Set strText equal to the code below (don't forget to include the form ID and make sure your quotes are correct):

<form name='qsd' id='Form2'>
<ilayer id="countdownnsmain" width=300; height=50; visibility=show>
<layer id="countdownnssub" width=300; height=50; left=0 top=0>
</layer>
</ilayer>
</form>

And remove that form from your ASPX page. This might get it working for you but no guarantees. Also in your ilayer and layer tags make sure they are formated properly. In some places you use ';' others you don't, around one attribute you have quotes and others you don't. Anyway, that's how I would approach making this work. Since I can't actually test this I can't tell you how it will play out, but even if it doesn't work 100% keep your eyes open for small things that might point you in the right direction. Good
luck! Ken.

Nov 18 '05 #29

P: n/a
Hello
As long as you use only english and western european characters (characters
from code page 1252) in your pages, your app will not be affected. But if you
need to display text in other languages (such as russian, chinese or arabic)
you will need to use utf-8. I think Netscape 4 doesn't support unicode, but I
am not sure. Any
ways this setting can be applied per page. by changing the @page directive
or using <location> tag in web.config

Best regards,
Sherif

"amos" wrote:
it works great,

just a question, when I change from utf8 to windows-1252,
will it change something for the rest of my app ?

"Sherif El-Metainy" <Sherif El********@discussions.microsoft.com> wrote in message news:<D8**********************************@microso ft.com>...
Hello

try changing this in web.config the globalization setting in web.config to
look like this
<globalization requestEncoding="windows-1252"
responseEncoding="windows-1252" fileEncoding="windows-1252" />

Best regards,
Sherif

"amos" wrote:
Sorry if you think I'm rude, it's just I asked a for an answer to the
question, not for any proverb. There is no hostility.

Concerning the problem, I just have to say that we don't understand
each other.

I tell you that the code in the navigator IS THE SAME
that the one I entered. And in the ASPX page it does not work
(when it works in a HTML or ASP page for example).

And I paste the javascript code in the HTML <HEAD> section,
it's not in a server object.

All other Javascript code I write works on all the navigators.

So that's why I insist on this point, there must be a bug somewhere
in the DotNet section.

When you use the instruction doucument.layername.write,
it makes strange caracters appearing on the screen.

You can only see this in NETSCAPE4 since it's the only known
browser that displays LAYERS.

Am I Clear enough ?


"Scott M." <No****@NoSpam.com> wrote in message news:<ea*************@TK2MSFTNGP11.phx.gbl>...
> There is no reason for you to be rude.
>
> My response to your post had nothing to do with ego, so put your hostilities
> in check please and read what all of us have been saying to you. It seems
> that perhaps you DO need some lessons in ASP.NET because we're all telling
> you the same thing and you don't seem to be getting what we are trying to
> say.
>
> .NET has absolutely NOTHING to do with client-side code that you've embedded
> into your page (HTML or JavaScript). Now, if you are embedding your code
> into SERVER tags or what you've added CONFLICTS with SERVER tags, you'll
> have a problem. There's no bug. ASP.NET has been out for nearly 3 years
> now (longer if you include the beta period). It is more likely that you
> haven't yet fully learned how ASP.NET pages render their results.
>
> A .NET page, generated by VS.NET will automatically create a SERVER SIDE
> <Form> tag. If you've also added your own client-side <Form> tag, you've
> got to make sure that is kept separate from the server-side form tag.
>
> The bottom line is that if you simply view the code that was delivered to
> the client (by choosing View...Source from the rendered page in the
> browser), you can clearly see what .NET has rendered. If what you see there
> is not what you started with, then you've entered your code inappropriately
> in the first place (probably in the wrong area).
>
>
> "amos" <so**@caramail.com> wrote in message
> news:dd**************************@posting.google.c om...
> > 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.

Nov 18 '05 #30

This discussion thread is closed

Replies have been disabled for this discussion.