I tried to use both DOJO 0.3 and MochKit 1.4 : PACKED VERSION. Whilie
dojo loads I can never get to load MochiKit. The script I used on the
HTML page are
I have found a problem with MochiKit Base.js and the intrusion
protection system at work. The IPS truncates Base.js because it
assigns the unescape() function to a variable (in parseQueryString(),
line 1225 in version 1.4.2 of Base.js). The IPS response is documented
Per's suggested modification is not blocked.
On Jul 17, 4:07 pm, Per Cederberg cederb...@gmail.com wrote:
Now that I'm awake, it strikes me that this might be the obvious solution:
I'm trying to find an example of how to add tostring to a date
object so serializeJSON will work correctly. I see in the docs there
are many ways to do this.
I can't find an example anywhere. How are most people doing this? I
don't think prototyping in a __json__ or json method to the date
Once I workaround my last post of opening a logging pane in an window
with an invalid (IE) name, I get an error while loading messages.
In the following code, the 'this' is the window. logger is a valid
object that has a getMessages function, simply remove the 'this'?
var loadMessages =
Looks like a pretty slick way to achieve what you are looking for...
I'm not sure how cross-browser it is...
On 1/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
In python we have the handy in operator:
if 3 in [1,2,3]: ...
I just updated my code to the current revision and it seems to have
broken some of the dom functions. If I use a slightly modified string
of the DOM documentation and evaluate:
I just came across MochiKit for the first time the other day and the
website at first gave me the impression that the project is dormant.
The About page does not mention IE 7 or Firefox 2 -- are they
supported? And there hasn't been a blog entry since 2006-09-22.
I'm not sure whether this is still relevant to the current version of
MochiKit (I'm not using MK at all, just groping with similar issues),
but I just noticed that IE 6 gives a 'type mismatch' when I try to
assign null to onreadystatechange. That is probably b/c XMLHTTPRequest
is an ActiveX
I've played with this a bit more and have found that the
scaleMode.originalHeight and scaleMode.originalWidth aren't getting
set properly if the original values are 'auto' and the element is
hidden prior to the call to blindDown (and I suspect slideDown, etc
suffer the same problem). I was able
Just tested slideDown, it exhibits the same behavior. I've put in
essentially the same fix but it seems to have a horizontal positioning
problem if the element starts out hidden until the element is
/** @id MochiKit.Visual.slideDown */
MochiKit.Visual.slideDown = function
Below are the diffs from Visual.js which include four new functions
for sliding elements on/off to the left/right and two for sliding
pairs of elements together, one on and one off, and one for sliding
pairs of elements in a direction relative to their position in the
The diffs also include
Here's an updated blindDown, had a syntax error that showed up in
Firefox but not in Safari/WebKit:
/** @id MochiKit.Visual.slideDown */
MochiKit.Visual.slideDown = function (element, /* optional */ options)
Slide an element down.
It needs to have the content of the element
Ok, had a couple visual glitches that are now fixed with the patch
--- Visual.js (revision 1383)
+++ Visual.js (working copy)
@@ -1431,14 +1431,16 @@
Your patch notes indicate not using getElementWidth and
getElementHeight, what are the preferred?
In a fit of trying to get horizontal scaling to happen at the same
time as sliding a pair in the case where they were not the same size,
I had already migrated some of the duplications to helper
Thank you for your response.
The problem occurs even if only the MochiKit.Base module is included when
MochiKit.js is built, and even if globals are not exported. If you delete
everything below the opening comment block (w/ the Copyright notice) it
works just fine, however. (-:
I have some additional information on this problem. First of all, the issue
doesn't appear to be specific to MockiKit; I tried including the Dojo
toolkit, and saw exactly the same behaviour. Secondly, the problem seems to
be an interaction between Google's back-end, IE, and my code. In short:
Mail list logo