On 15 fév, 08:15, iain duncan [EMAIL PROTECTED] wrote:
are the get/setElementPosition functions intended to be used only with
and within fixed position elements? I am getting very different
behaviour between firefox and ie6 if any of the elements are absolute
( container or the moving
Hi Arnar -- Thx for your response: Yes, as you mentioned
getLoginStatus was calling right way and I was keep increasing and end
up with 5000. After modifying the statement to
MochiKit.Async.callLater(5000, getLoginStatus, token) , it solved
issues. Also I made another sample test script, which
Thanks for the reply Thomas
I don't think you meant 'fixed'. Fixed position doesn't even work
under IE.
Yeah, I just discovered that. Ugh. I'm a little irritated at how much
the Meyer book glosses over the fact that half of what's in there is
unusable ... :/
getElementPosition should give
On 2/15/07, Rush Manbert [EMAIL PROTECTED] wrote:
Hi all,
In my loadJSONDoc() callback I called a object constructor with an
incorrect argument list. The constructor detected this. Had I been
writing this in C++ (ignoring the fact that you can't call a function
with the wrong argument list
This should be fixed now. Please try the latest version in trunk.
On 14-Feb-07, at 4:34 AM, Pearl wrote:
Why is observers not defined runtime error coming? The following is
the error. How this can be avoided ?
A runtime error has occurred.
Line: 4206
Error: 'length' is null or not an
Maybe this is an oversight, maybe it's by design so you always get
some valid input from repr; I'm not sure but here's my suggestion.
- Aaron
===
--- Base.js (revision 1269)
+++ Base.js (working copy)
@@ -742,6 +742,9 @@
