IE fileCreatedDate undefined??

[NeoAlchemy]

Has anyone came across a situation or know how the
document.fileCreatedDate property could be throw a JScript Error in
IE6 browsers?

I am using this in a function to help determine an IE browser (with
other properties). It has been reported to me to fail in others
browser. Since it works on other peoples machines I would make me
think is there something that can be done to a webpage that can have
this cause an issue.

 

[Evertjan.]

NeoAlchemy wrote on 20 jun 2007 in comp.lang.javascript:

Has anyone came across a situation or know how the
document.fileCreatedDate property could be throw a JScript Error in
IE6 browsers?

Meseems you only have to misspell it
to have javascript give an error in IE6 and other browsers.

Try:

document.fileCreaxxxxxxtedDate()

I am using this in a function to help determine an IE browser (with
other properties). It has been reported to me to fail in others
browser. Since it works on other peoples machines I would make me
think is there something that can be done to a webpage that can have
this cause an issue.

If it works in other browsers, say FF2,
you would no longer be able to determine IE as the browser.

What issue would you have it caused?

=====================

Are we perchance miscommunicating?

 

[Randy Webb]

NeoAlchemy said the following on 6/20/2007 8:58 AM:

Has anyone came across a situation or know how the
document.fileCreatedDate property could be throw a JScript Error in
IE6 browsers?

I am using this in a function to help determine an IE browser (with
other properties).

IE is so trivial to determine so why are you trying to make it so
difficult? Conditional Compilation is your friend.

 

[-Lost]

NeoAlchemy said the following on 6/20/2007 8:58 AM:

IE is so trivial to determine so why are you trying to make it so
difficult? Conditional Compilation is your friend.

How would conditional compilation help in this scenario? I don't know
too much about it, so, feel free to dumb it down.

 

[Randy Webb]

-Lost said the following on 6/20/2007 7:49 PM:

How would conditional compilation help in this scenario? I don't know
too much about it, so, feel free to dumb it down.

If I wanted to identify IE6? Simple:

<!--[if IE 6]>
<script>
alert('What browser alerts this other than IE6?')
</script>
<![endif]-->

 

[NeoAlchemy]

Well, the solution needs to work in a script only and not in html so I
can't use conditional compilation. The purpose is for an object
detection test in an external script for others to use. It also must
fail for IE MAC. I think that is why I used the fileCreatedDate, if
not I'd have to check the other conditionals with it.

Evertjan, I guess what I was meaning to say is that the function the
user is testing works in other scenarios for testing if object
exists. For some reason, including the function within his scripts it
doesn't work in one scenario but does in another scenario.

My thoughts were the object fileCreatedDate might not work if the html
page containing the script downloaded improperly.

 

[Evertjan.]

NeoAlchemy wrote on 21 jun 2007 in comp.lang.javascript:

Well, the solution needs to work in a script only and not in html so I

What solution?

can't use conditional compilation. The purpose is for an object
detection test in an external script for others to use. It also must
fail for IE MAC. I think that is why I used the fileCreatedDate, if
not I'd have to check the other conditionals with it.

Evertjan, I guess what I was meaning to say is that the function the
user is testing works in other scenarios for testing if object
exists. For some reason, including the function within his scripts it
doesn't work in one scenario but does in another scenario.
????

My thoughts were the object fileCreatedDate might not work if the html
page containing the script downloaded improperly.

This is usenet.without quoting, how would I [and more important others on
this NG] know what we where discussing?
[please always quote on usenet]

If the subject is: "IE fileCreatedDate undefined??",
how can it be that he unquoted so elusive script "need to work" in "script
only"?

 

[NeoAlchemy]

This is usenet.without quoting, how would I [and more important others on

this NG] know what we where discussing?
[please always quote on usenet]

Ok, let me start my reply over....

Meseems you only have to misspell it
to have javascript give an error in IE6 and other browsers.
Try: document.fileCreaxxxxxxtedDate()

Well, in that case your not getting an error due to
document.fileCreatedDate

If I wanted to identify IE6? Simple:

<!--[if IE 6]>
<script>
alert('What browser alerts this other than IE6?')
</script>
<![endif]-->

I only meant that the error was occuring in IE6. The object detection
needs to work for IE browsers 5.0 and above and on windows only. The
object detection is wrapped around a function that is included in an
external javascript file. So trying to identify IE only can't be done
by conditional compilations.

 

[Randy Webb]

NeoAlchemy said the following on 6/21/2007 12:16 PM:

This is usenet.without quoting, how would I [and more important others on
this NG] know what we where discussing?
[please always quote on usenet]

Ok, let me start my reply over....

And here I was thinking that not quoting was annoying. Copy/pasting,
without attributing it, is 10 times worse.

If I wanted to identify IE6? Simple:

<!--[if IE 6]>
<script>
alert('What browser alerts this other than IE6?')
</script>
<![endif]-->

I only meant that the error was occuring in IE6.

The error isn't occurring in IE6 if it doesn't occur repeatedly in
different IE 6'es. What you are hunting is a version of the jscript.dll
that is throwing the errors. Then you want to isolate that version. Have
the people that are getting the errors give you the version of the
jscript.dll file and see if you can find a pattern where particular
versions give problems while others don't. You can update the
jscript.dll file without updating the browser.

The object detection needs to work for IE browsers 5.0 and above
and on windows only.

Are you using fileCreatedDate for anything other than trying to isolate
IE? If you are using it solely for isolation then you aren't object
detecting, you are browser detecting.

The object detection is wrapped around a function that is included in an
external javascript file. So trying to identify IE only can't be done
by conditional compilations.

I bet it can. I would also bet it is the most fool-proof (at the moment
anyway) method to try to isolate IE. What I posted was Conditional
Comments, Conditional Compilation is a totally different matter. One is
HTML, the other is Scripting.

 

[NeoAlchemy]

NeoAlchemy said the following on 6/21/2007 12:16 PM:


The error isn't occurring in IE6 if it doesn't occur repeatedly in
different IE 6'es. What you are hunting is a version of the jscript.dll
that is throwing the errors. Then you want to isolate that version. Have
the people that are getting the errors give you the version of the
jscript.dll file and see if you can find a pattern where particular
versions give problems while others don't. You can update the
jscript.dll file without updating the browser.

Nice idea, I'll look into that. The actual browser detection might
work for one html page but not another html page.

I bet it can. I would also bet it is the most fool-proof (at the moment
anyway) method to try to isolate IE. What I posted was Conditional
Comments, Conditional Compilation is a totally different matter. One is
HTML, the other is Scripting.

Thanks for that hint. Your right I got conditional compilations mixed
up with conditional comments. I can use conditional compilation to
better determine the function.

 

[Evertjan.]

NeoAlchemy wrote on 21 jun 2007 in comp.lang.javascript:

Nice idea, I'll look into that.

The actual browser detection might
work for one html page but not another html page.

Why would that be?
By having different html on such pages?
I doubt that.

 

[Dr J R Stockton]

In comp.lang.javascript message <ubidnXL2KOkiIeTbnZ2dnUVZ_gSdnZ2d@comcas

How would conditional compilation help in this scenario? I don't know
too much about it, so, feel free to dumb it down.

<FAQENTRY> That's a topic, IMHO, that should appear in the FAQ.

In the FAQ, the link following
Microsoft (D)HTML reference:-
needs attention.

A search at the redirected page for "conditional" finds, as the first of
19470 hits, what looks as if it would be a suitable reference - except
that the link is broken.

Link <http://msdn.microsoft.com/library/default.asp?url=/library/en-
us/script56/html/a843de4e-3aae-43cd-ad64-477dd00814a2.asp> for
conditional compilation works, and might show a better solution.

 

[Randy Webb]

Dr J R Stockton said the following on 6/21/2007 4:08 PM:

In comp.lang.javascript message <ubidnXL2KOkiIeTbnZ2dnUVZ_gSdnZ2d@comcas


<FAQENTRY> That's a topic, IMHO, that should appear in the FAQ.

It has been discussed before. The only reason for CC is browser
detection and it is hypocritical to show how to browser detect and then
have the FAQ say it is a bad idea.

In the FAQ, the link following
Microsoft (D)HTML reference:-
needs attention.

A search at the redirected page for "conditional" finds, as the first of
19470 hits, what looks as if it would be a suitable reference - except
that the link is broken.

Link <http://msdn.microsoft.com/library/default.asp?url=/library/en-
us/script56/html/a843de4e-3aae-43cd-ad64-477dd00814a2.asp> for
conditional compilation works, and might show a better solution.

For me, that link redirects to
<URL: http://msdn2.microsoft.com/en-us/library/121hztk3.aspx>

 

[Dr J R Stockton]

Dr J R Stockton said the following on 6/21/2007 4:08 PM:

It has been discussed before. The only reason for CC is browser
detection and it is hypocritical to show how to browser detect and then
have the FAQ say it is a bad idea.

Codswallop. It is a topic which those who read Web page sources are
liable to need to know something about, as it is undoubtedly used there.

There's nothing wrong with describing something as a bad idea in a FAQ -
but can you be sure that the only possible use for such detection is in
cases where feature detection can be used? Well, perhaps *you* can be
sure; but is it true? I rather doubt it.

How's the next version of the FAQ progressing? Every day for which your
wonderful new work is unpublished is a day on which it can help no-one.