C
Charles Harrison Caudill
I've been going through tutorials, APIs, posts on this newsgroup, this
newsgroup's faq, etc...
I have a function that describes the fields that an object claims to have and
I have found what that function reports to often be contradictory to what it
will actually respond to. I have seen objects whose toString method returns
"[object inaccessible]" (which Google is unaware of practically btw) return a
correct value when I request the "name" field, but even though they are
supposed to be of a certain type, "name" is the only field it acknowledges
having. I've watched practically all example code fail utterly. I have
combed the APIs for Opera, Mozilla, IE and found many useful methods I'd like
to use that don't run. I've watched code work, then quit working because I
changed a name then changed it back. My opinion of javascript thus far can be
summarized in the following posit:
Javascript is non turing-compliant,
in a given state, with a given set of inputs it may or may not do the same
thing as the last time it was in that state with those inputs.
I've been trying to get a frame to shrink to fit the contents because some
browsers will render a table in such a manner that even though the sum of
heights of the cells at the side of a picture is smaller than the height of
the picture, and the cell spacing is set to 0, the browser still adds a
spacing causing the cells at the side to be taller than the picture.
I have two frames declared as follows:
<frameset rows="90,*" border="0" onload="resize()">
<frame
src="http://gtda.hypersphere.org/photo_header.html"
scrolling="no"
name="header"
id="header"
/>
<frame src="http://gtda.hypersphere.org/photo" />
</frameset>
for now, I'd be happy if I could get resize() to simply alert me of the height
of that document, or maybe if I could just get it to follow the api's, or
possibly if I could figure out why I can access the frame by getElementById
(sometimes), but never by document or parent.document .frames[0] or
..frames.item("header") or anything else like that.
I haven't seen something this nonsensical since Thermodynamics or maybe trying
to decipher the Linux VFS layer.
help me comp.lang.javascript, you're my only hope...
newsgroup's faq, etc...
I have a function that describes the fields that an object claims to have and
I have found what that function reports to often be contradictory to what it
will actually respond to. I have seen objects whose toString method returns
"[object inaccessible]" (which Google is unaware of practically btw) return a
correct value when I request the "name" field, but even though they are
supposed to be of a certain type, "name" is the only field it acknowledges
having. I've watched practically all example code fail utterly. I have
combed the APIs for Opera, Mozilla, IE and found many useful methods I'd like
to use that don't run. I've watched code work, then quit working because I
changed a name then changed it back. My opinion of javascript thus far can be
summarized in the following posit:
Javascript is non turing-compliant,
in a given state, with a given set of inputs it may or may not do the same
thing as the last time it was in that state with those inputs.
I've been trying to get a frame to shrink to fit the contents because some
browsers will render a table in such a manner that even though the sum of
heights of the cells at the side of a picture is smaller than the height of
the picture, and the cell spacing is set to 0, the browser still adds a
spacing causing the cells at the side to be taller than the picture.
I have two frames declared as follows:
<frameset rows="90,*" border="0" onload="resize()">
<frame
src="http://gtda.hypersphere.org/photo_header.html"
scrolling="no"
name="header"
id="header"
/>
<frame src="http://gtda.hypersphere.org/photo" />
</frameset>
for now, I'd be happy if I could get resize() to simply alert me of the height
of that document, or maybe if I could just get it to follow the api's, or
possibly if I could figure out why I can access the frame by getElementById
(sometimes), but never by document or parent.document .frames[0] or
..frames.item("header") or anything else like that.
I haven't seen something this nonsensical since Thermodynamics or maybe trying
to decipher the Linux VFS layer.
help me comp.lang.javascript, you're my only hope...