> Once requested, it's going to finish downloading no matter what
> js-foo you throw at it.
Load image as IFRAME src, remove IFRAME mid-download. IFRAMEs have
their own window so kills background WK download thread as well.
Tested Chrome 6, Saf 5.
-- S.
This sounds like a bug. If you'll file it at lighthouse (
https://mootools.lighthouseapp.com/projects/24057-mootoolsmore) we'll work
on it for 1.2.5.
On Fri, Sep 17, 2010 at 7:19 PM, Enric wrote:
> Hi, I am working in a project in which we updated to mootools 1.2.5.
> Some problems appeared in f
Hi, I am working in a project in which we updated to mootools 1.2.5.
Some problems appeared in functions that are triggered (...fired) by
event delegation.
With mootools 1.2.4 "this" inside that functions referes to the
element where the event is delegated that matches the selector, and
with 1.2.5
Welcome to the dev list.
On Sep 17, 2010, at 5:13 PM, Aaron Newton wrote:
> sometimes I am unwillingly insulting Aaron because I use the
> wrong words - but in the end, language is the least of our problems.
>
> Christoph, for the last time, calling me a "troglodytic bastard" is not
> exactly a
>
> sometimes I am unwillingly insulting Aaron because I use the
> wrong words - but in the end, language is the least of our problems.
>
Christoph, for the last time, calling me a "troglodytic bastard" is not
exactly a case of poor translation...
/kidding
Haha, good one Aaron, I should add that to my invites too.
Aaron's list is a pretty good summary what you can do to get involved.
We want users to start getting active themselves. This is the only way
open source can work. If someone starts to contribute to MooTools, it
won't take long until we re
Sounds to me like this is the same issue as image replacement of lazy loading.
https://bugs.webkit.org/show_bug.cgi?id=6656
If you destroy the element, it'll stop loading in a lot of browser, but not
webkit. Once requested, it's going to finish downloading no matter what js-foo
you throw at it
If I am loading an image with asset.image, is it in any way possible
to abort loading when it's running? Like forcing the onabort, doing
the stuff the browser stop button does to images, except that I don't
want to "execute" the stop button (and stop the whole page/window).
I have this image stack
Keep in mind that the devs are the most active people on the user list.
Anyone looking for us doesn't have to try too hard.
> It's though possible that my assumptions about dev list content are
> incorrect and all that I say here doesn't make sense (is it really as
> "... difficult"? ;)
>
Here's
We still keep the 1.1 docs online (http://docs111.mootools.net/) so rest
assured that we'll keep them available.
On Fri, Sep 17, 2010 at 11:32 AM, batman42ca wrote:
> With version 1.3.0 getting closer to a release date, what happens to
> the documentation currently on the mootools,net web site?
First, thanks to all for patience ;)
On 17 сен, 17:27, Slik Jay wrote:
> This is not developers problem, this is user's problem.
> If user interested in mootools development, he can join #mootools IRC
> chanel on irc.freenode.net, he can follow mootools developers on
> github (user doesn't know m
With version 1.3.0 getting closer to a release date, what happens to
the documentation currently on the mootools,net web site? My limited
understanding is that 1.3.0 will be somewhat different from 1.2.x
(with perhaps a backwards compatibility layer?).
Will 1.2.x documentation still be available t
To my knowledge we never have asked anyone to leave. I realize you were
joking, but it might not have come across that way as sarcasm often fails to
in text...
On Fri, Sep 17, 2010 at 10:10 AM, Rajeev J Sebastian <
rajeev.sebast...@gmail.com> wrote:
> On Fri, Sep 17, 2010 at 9:52 PM, Aaron Newton
I played with this too and even replaced ref to this.getNext().set("html"
but it still messes up. Weird...
Sent from my iPhone
On 17 Sep 2010, at 04:34 PM, "Andrea Dessì" wrote:
Hi electronbender,
I've seen queekly your code and maybe the onComplete function,
passed to the request istance, doe
On Fri, Sep 17, 2010 at 9:52 PM, Aaron Newton wrote:
>> Also note that, unlike -users list, dev list and IRC channel can be a
>> bit ... difficult.
>
> Hah. an understatement!
> We're pretty quick to invite people to the dev list. The barrier to getting
> that invite is generally the following:
>
To clarify: the list below is an OR list not an AND list. You just have to
do one of those things, not all of them.
> We're pretty quick to invite people to the dev list. The barrier to getting
> that invite is generally the following:
>
>- you write a few blog posts that are about mootools
>
I'd like to say my opinion.
We have to admit what Aaron is saying is understandable,
and we all can accept it.
:)
I agree.
Andrea
On Fri, Sep 17, 2010 at 18:22, Aaron Newton wrote:
> Also note that, unlike -users list, dev list and IRC channel can be a
>> bit ... difficult.
>>
>
> Hah. an un
>
> Also note that, unlike -users list, dev list and IRC channel can be a
> bit ... difficult.
>
Hah. an understatement!
We're pretty quick to invite people to the dev list. The barrier to getting
that invite is generally the following:
- you write a few blog posts that are about mootools
Hi electronbender,
I've seen queekly your code and maybe the onComplete function,
passed to the request istance, doesn't know who is "chLip".
I think you have to use ".bind()" for that funcion...
Something like:
onComplete: function(theData){
this.set('html',theData.ve
MooDialog: http://www.mootools.net/forge/p/moodialog
On Sep 16, 11:46 pm, Oskar Krawczyk wrote:
> http://www.google.com/#hl=en&source=hp&q=mootools+modal+window&fp=1
>
> http://digitarald.de/project/squeezebox/
>
> On 2010-09-16, at 23:37, darpi wrote:
>
>
>
> > Hi,
> > I'm looking for a moda
Fx.CustomProp = new Class({
Extends: Fx,
initialize: function(element, options) {
this.element = document.id(element);
this.parent(options);
},
set: function(current) {
//my stuff
}
});
On Sep 17, 3:38
some idea, how-to?
I'm generating a list of articles like so:
data.articles.each(function(article, ind){
var chLi = new Element('li').inject(rootUl);
var chA = new Element('a',{'href':'javascript:;'}).inject(chLi);;
var chLih = new Element('h4').set('html',vest.title).inject(chA);;
var chLip = new Element('p').set('
2010/9/17 Mikhail Korobov :
> I'm a mootools user for several years (since 1.2 release) and only now
> I realized that there is a private dev list. I wasn't able to ask an
> invite because I wasn't aware this list exists. So there is no entry
> point for average developer. What average developer wo
> I'm a mootools user for several years (since 1.2 release) and only now
> I realized that there is a private dev list. I wasn't able to ask an
> invite because I wasn't aware this list exists. So there is no entry
> point for average developer. What average developer would do if he
> want to know
I'm a mootools user for several years (since 1.2 release) and only now
I realized that there is a private dev list. I wasn't able to ask an
invite because I wasn't aware this list exists. So there is no entry
point for average developer. What average developer would do if he
want to know what is ha
The idea is to get in touch with one of the devs on IRC or GTalk.
Communication is key, it is the easiest and best way to get involved.
Feel free to add me http://cpojer.net
On Sep 17, 11:24 am, Rolf -nl wrote:
> Right... this simple question started a nice conversation ;) I think
> there's somet
Done
https://mootools.lighthouseapp.com/projects/2706-mootools/tickets/1009-new-dategetweek-returns-the-wrong-week-number
Right... this simple question started a nice conversation ;) I think
there's something to be said about both views*. Though as it seems to
"work" at this moment, best would be to stay this way. Maybe the dev
list people can keep a short changelog up-to-date with decisions made
which is read only (a
> Am I missing something?
Looked at it and I think you've found a bug -- put it in the
Lighthouse tracker.
(260/7).ceil() == 38
The algo is way too simplistic, though not alone in webland. This
well-circulated "expert guide" is also wrong. :P
http://javascript.about.com/li
Today example it is still week 37, but "new Date().get('week')"
returns week 38.
The returned date when console logging "new Date()" is correct.
Am I missing something?
31 matches
Mail list logo
