I checked in a workaround in revision 1225.
Can you verify it corrects your problem ? Thanks.
--
Thomas
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
MochiKit group.
To post to this group, send email to
This could be useful to have a fast way of changing many elements that
have a common CSS class.
it has been tested on IE/Firefox, not safari.
it should work well on differents browsers, provided you use basic CSS
selectors, like
.myclass or div.myclass
{{{
function changeCSSProperty(pSelector,
Diez B. Roggisch a écrit :
So - is there any chance such a thing could be made (optionally) part of the
Async-package?
If a patch is provided, why not. Until then, you have several options:
* define the cache control in your web server (with pragma no-cache and
cache-control).
* Add an
That works, thanks!
Jason
From: Thomas Hervé [EMAIL PROTECTED]
To: MochiKit mochikit@googlegroups.com
Subject: [mochikit] Re: Color.fromBackground broken in IE 7?
Date: Wed, 29 Nov 2006 03:08:17 -0800
I checked in a workaround in revision 1225.
Can you verify it corrects your problem ?
Hi,
me again - I ran into troubles when trying and getting onkeyup-events working
with IE6.
What I do is this:
--
function print_event(event) {
s = '';
for(var p in event) {
s += p + = + event[p] + : ;
}
alert(s);
};
function test() {
var form =
On 11/29/06, Diez B. Roggisch [EMAIL PROTECTED] wrote:
Beau Hartshorne schrieb:
I don't understand what the problem is. Is e.key().string not
returning the correct values?
By the way, you don't need to iterate over the event object. It has a
repr() method, so you can just do something
According to this thread:
href=http://groups.google.com/group/mochikit/browse_thread/thread/7b9e83aaaba4ec2/80ad93582b0a22b0?lnk=gstq=memory+leakrnum=3#80ad93582b0a22b0
The memory leak in the connect function was fixed in the trunk. Was
1.3.1 supposed to include this fix. I just wrote a
On 29-Nov-06, at 8:50 PM, DJK wrote:
According to this thread:
href=http://groups.google.com/group/mochikit/browse_thread/thread/
7b9e83aaaba4ec2/80ad93582b0a22b0?lnk=gstq=memory
+leakrnum=3#80ad93582b0a22b0
The memory leak in the connect function was fixed in the trunk. Was
1.3.1
