Unknown runtime error

[sheldonlg]

I have googled for '"Internet Explorer" "Unknown runtime error"' and not
found anything useful. I have the following (for simplicity of
presentation here):

<div><table><tr ><th id="foo"></th></tr></table></div>

In my javascript I have two lines:

var titleObj = document.getEle mentById('foo') ;
titleObj.innerH TML = "Name is bar";

IE6 is throwing an "Unknown runtime error" at the second line.

What can I do about it?

[nobody]

On Thu, 08 May 2008 15:06:39 +0200, Thomas 'PointedEars' Lahn
<Po*********@we b.dewrote:

>Therefore it is not possible
to stick to MS VS.NET for the development of client-side scripts without
irresponsibl y ignoring the many other execution environments out there.
PointedEars

Fully agree on this one. My approach is - write in one environment
(accidentally it's VS.NET because it integrates well with my
server-side environment), test - and quite often do
if(isIE){//IE-specific;} if(isFF){//Firefox-specific;}... - in all
target environments. Sometimes (more often than I'd like it to happen)
it's not possible to write to the lowest common denominator due to the
lack thereof, therefore the branching. Though IMO it is not due to
syntax or scripting engine differences but rather due to differences
in document object models. Yet there's nothing better than VS.NET to
debug IE-specific and common code, so much so that I badly miss it
when I have to use Venkman for FF branches. Definitely VS.NET is not
even comparable to MS script debugger - this one is in the same class
as Venkman.

NNN

[Thomas 'PointedEars' Lahn]

no****@nowhere. net wrote:

[...] Thomas 'PointedEars' Lahn [...] wrote:

>Therefore it is not possible
to stick to MS VS.NET for the development of client-side scripts without
irresponsibl y ignoring the many other execution environments out there.
[...]

Please trim your quotes, especially avoid quoting signatures.

Fully agree on this one. My approach is - write in one environment
(accidentally it's VS.NET because it integrates well with my
server-side environment), test - and quite often do
if(isIE){//IE-specific;} if(isFF){//Firefox-specific;}... - in all
target environments.

While it is good to see that after all this time you are telling about you
are able to differentiate between host environments and their associated
AOM/DOM, you still have to learn to differentiate between execution/runtime
environments, i.e. ECMAScript implementations . I was more referring to mere
differences between the language implementations , and between their versions
that you would be dealing with, instead. For example, the terms
"IE-specific" and "Firefox-specific" are not covering the differences
between JScript and JavaScript, whereas the former is used by all versions
of the MSHTML browser component, and the latter is used by *all* Gecko-based
UAs (in different versions each), and they are ignoring other implementations .

See also http://PointedEars.de/es-matrix (I am going to add and test more
implementations , particularly Opera ECMAScript, and Apple JavaScriptCore as
of Safari 3.1 for Windows).
PointedEars
--
Use any version of Microsoft Frontpage to create your site.
(This won't prevent people from viewing your source, but no one
will want to steal it.)
-- from <http://www.vortex-webdesign.com/help/hidesource.htm>