Annoying flaw / bug in ASP.NET

I think there is a flaw/bug in ASP.NET or IIS. I try to test my pages
in Firefox Browser because it's better than IE (page source coloring,
tabbed browsing, etc.) but the JavaScript that is generated for ASP.NET
compile errors doesn't work on Firefox (try clicking on the JavaScript
link to view the complete code). I'm using ASP.NET/C# on Windows XP
Pro/IIS. I'm getting JavaScript errors from the ASP.NET generated
javascript: "window.event has no properties."

This is what it looks like (I don't know JavaScript) --

<script language="JavaScript">
function OnToggleTOCLevel1()
{
var elemSrc = window.event.srcElement;
var elemLevel2 = document.all(elemSrc.level2ID);

if (elemLevel2.style.display == 'none')
{
elemLevel2.style.display = '';
if (elemSrc.usesGlyph == '1')
elemSrc.innerHTML = '6';
}
else {
elemLevel2.style.display = 'none';
if (elemSrc.usesGlyph == '1')
elemSrc.innerHTML = '4';
}
}
</script>

re: Annoying flaw / bug in ASP.NET

This looks like the source you'd see if there is a compiler error on
the ASPX page.

My suggestion would be to view the page in IE until you can fix the
compiler error. All of the basic ASP.NET controls work pretty well
with FireFox, I think, although I have not done extensive testing in
that area.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Sun, 05 Jun 2005 19:34:06 -0400, nospam <nospam@no-spam1314143.com>
wrote:
[color=blue]
>I think there is a flaw/bug in ASP.NET or IIS. I try to test my pages
>in Firefox Browser because it's better than IE (page source coloring,
>tabbed browsing, etc.) but the JavaScript that is generated for ASP.NET
>compile errors doesn't work on Firefox (try clicking on the JavaScript
>link to view the complete code). I'm using ASP.NET/C# on Windows XP
>Pro/IIS. I'm getting JavaScript errors from the ASP.NET generated
>javascript: "window.event has no properties."
>
>This is what it looks like (I don't know JavaScript) --
>
><script language="JavaScript">
>function OnToggleTOCLevel1()
>{
> var elemSrc = window.event.srcElement;
> var elemLevel2 = document.all(elemSrc.level2ID);
>
> if (elemLevel2.style.display == 'none')
> {
> elemLevel2.style.display = '';
> if (elemSrc.usesGlyph == '1')
> elemSrc.innerHTML = '6';
> }
> else {
> elemLevel2.style.display = 'none';
> if (elemSrc.usesGlyph == '1')
> elemSrc.innerHTML = '4';
> }
>}
></script>[/color]

re: Annoying flaw / bug in ASP.NET

Scott Allen wrote:[color=blue]
> This looks like the source you'd see if there is a compiler error on
> the ASPX page.
>
> My suggestion would be to view the page in IE until you can fix the
> compiler error. All of the basic ASP.NET controls work pretty well
> with FireFox, I think, although I have not done extensive testing in
> that area.
>
> --
> Scott
> http://www.OdeToCode.com/blogs/scott/[/color]

I realize that the solution is to view the page in IE. I'm just
pointing out that there is a bug. One thing that I have noticed is that
ASPX pages often only display correctly in IE and not in Firefox. I
would just write it off to bad programming but it's something that I
find very often and even in books like Beginning ASP.NET 1.1 in C# by
Matthew MacDonald (which I am learning from). I am running the sample
code in Firefox and some of it doesn't display correctly.

re: Annoying flaw / bug in ASP.NET

That is most likely caused by your Browsercaps section
in either machine.config or web.config not having an
appropiate entry for Firefox, .

Go to : http://slingfive.com/pages/code/brow...aps_spaces.txt
and modify your application's web.config or your server's machine.config
per the code at that page and that should allow browsing your websites
with Firefox, Mozilla, Konqueror, Opera and Mac's Safari browser.



Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
======================

"nospam" <nospam@no-spam1314143.com> wrote in message
news:11a7b2ghetmqi79@corp.supernews.com...[color=blue]
> Scott Allen wrote:[color=green]
>> This looks like the source you'd see if there is a compiler error on
>> the ASPX page. My suggestion would be to view the page in IE until you can fix the
>> compiler error. All of the basic ASP.NET controls work pretty well
>> with FireFox, I think, although I have not done extensive testing in
>> that area. --
>> Scott
>> http://www.OdeToCode.com/blogs/scott/[/color]
>
> I realize that the solution is to view the page in IE. I'm just pointing out that there
> is a bug. One thing that I have noticed is that ASPX pages often only display correctly
> in IE and not in Firefox. I would just write it off to bad programming but it's
> something that I find very often and even in books like Beginning ASP.NET 1.1 in C# by
> Matthew MacDonald (which I am learning from). I am running the sample code in Firefox
> and some of it doesn't display correctly.[/color]

re: Annoying flaw / bug in ASP.NET

I concur with Señor Libre. By default ASP.NET does not even know Firefox and
thus it would be considered as a downlevel browser.

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




"Juan T. Llibre" <nomailreplies@nowhere.com> wrote in message
news:ODDYMVkaFHA.3840@tk2msftngp13.phx.gbl...[color=blue]
> That is most likely caused by your Browsercaps section
> in either machine.config or web.config not having an
> appropiate entry for Firefox, .
>
> Go to : http://slingfive.com/pages/code/brow...aps_spaces.txt
> and modify your application's web.config or your server's machine.config
> per the code at that page and that should allow browsing your websites
> with Firefox, Mozilla, Konqueror, Opera and Mac's Safari browser.
>
>
>
> Juan T. Llibre
> ASP.NET MVP
> http://asp.net.do/foros/
> Foros de ASP.NET en Español
> Ven, y hablemos de ASP.NET...
> ======================
>
> "nospam" <nospam@no-spam1314143.com> wrote in message
> news:11a7b2ghetmqi79@corp.supernews.com...[color=green]
>> Scott Allen wrote:[color=darkred]
>>> This looks like the source you'd see if there is a compiler error on
>>> the ASPX page. My suggestion would be to view the page in IE until you
>>> can fix the
>>> compiler error. All of the basic ASP.NET controls work pretty well
>>> with FireFox, I think, although I have not done extensive testing in
>>> that area. --
>>> Scott
>>> http://www.OdeToCode.com/blogs/scott/[/color]
>>
>> I realize that the solution is to view the page in IE. I'm just pointing
>> out that there is a bug. One thing that I have noticed is that ASPX
>> pages often only display correctly in IE and not in Firefox. I would
>> just write it off to bad programming but it's something that I find very
>> often and even in books like Beginning ASP.NET 1.1 in C# by Matthew
>> MacDonald (which I am learning from). I am running the sample code in
>> Firefox and some of it doesn't display correctly.[/color]
>
>[/color]

re: Annoying flaw / bug in ASP.NET

A bug is when an application does not behave as designed. What you are
describing is not a bug. In fact, it is perfectly possible to design ASP.Net
pages that work well in all browsers. But you have to know a bit more about
ASP.Net, as well as browsers, in order to do so.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Ambiguity has a certain quality to it.

"nospam" <nospam@no-spam1314143.com> wrote in message
news:11a7b2ghetmqi79@corp.supernews.com...[color=blue]
> Scott Allen wrote:[color=green]
>> This looks like the source you'd see if there is a compiler error on
>> the ASPX page. My suggestion would be to view the page in IE until you
>> can fix the
>> compiler error. All of the basic ASP.NET controls work pretty well
>> with FireFox, I think, although I have not done extensive testing in
>> that area. --
>> Scott
>> http://www.OdeToCode.com/blogs/scott/[/color]
>
> I realize that the solution is to view the page in IE. I'm just pointing
> out that there is a bug. One thing that I have noticed is that ASPX pages
> often only display correctly in IE and not in Firefox. I would just write
> it off to bad programming but it's something that I find very often and
> even in books like Beginning ASP.NET 1.1 in C# by Matthew MacDonald (which
> I am learning from). I am running the sample code in Firefox and some of
> it doesn't display correctly.[/color]