Re: [Moo] Re: "empty" function on new HtmlTable fails

Looks like there's a fix for this https://github.com/mootools/mootools-more/issues/1081 On Monday, March 12, 2012 8:15:34 PM UTC-4, Nutron wrote: > > This alone seems a bug to me. > > new HtmlTable().empty(); >> Uncaught TypeError: Cannot call method 'isDisplayed' of undefined >> > > File it in

[Moo] Re: Copy of accordion demo does not work under IE8?

It looks like you need to add a doctype to your page. As of right now IE is rendering in "quirksmode" and not "standards". >From the docs: Notes - *Fx.Accordion* requires the page to be in Standards Mode . http://mootools.net/docs/more/Fx/Fx.Accordion

[Moo] Re: elements to replace one element - how? (quickest way)

For what it's worth, I believe the `replaceChild` was causing errors for some reason (granted I'm horrid at writing out those tests so that probably isn't the real issue). Anyhow... I made a test with an array of 500 spans and used the single injection per iteration method and one with creating

[Moo] Re: elements to replace one element - how? (quickest way)

Awesome, I wanted to do a perf test too but I suck at making them it seems... I tried adding one more performance test with document fragments but it errors :( http://jsperf.com/docfrag-textnode-insertion/4

[Moo] Re: elements to replace one element - how? (quickest way)

you really don't need a fragment for that. this: var elements = $$('span'); elements.each(function(elm){ var fragment = document.createDocumentFragment(); fragment.appendChild(document.createTextNode('X')); elm.parentNode.insertBefore(fragment, elm.nextSibling); }); could just be: v

[Moo] Re: elements to replace one element - how? (quickest way)

Okay sorry, this might be of more help? To get away from using `inject` on each element iteration in your array and just using the `replaceChild` you could do as Ger recommended and add them all to a parent node. If you used a document fragment you wouldn't have a leftover wrapper element when

[Moo] Re: elements to replace one element - how? (quickest way)

You could implement your own `replaces` function within Elements. http://jsfiddle.net/subhaze/AfeBV/ Elements.implement('replaces', function(old, where){ if(!old) return; var _where = where || 'after', _old = document.id(old); this.inject(_old, _where); _old.destroy(); });

Re: [Moo] Feedback on Element.implement

Awesome man!

Re: RE: [Moo] Feedback on Element.implement

One issue I see with using onComplete wired the way it is, is that it causes the element to pulse on any tween after the pulse method has been used. As in this example http://jsfiddle.net/subhaze/EppqN/1/ if you click pulse first then click tween color the element will pulse after tweening its c

[Moo] Re: Getting 1.3.2 ready for release - Testing

Here are the results I got on my win7 64 laptop, IE6-8 and FFx3.6 were ran in .VHDs that are provided by MS for IE version testing * * *Chrome *10.0.648.205 *win7(64)* [core/more client specs] (hundreds, all seemed to be based off these two errors) - `TypeError: Object [object HTMLDivEleme

Re: [Moo] Re: how to filter elements by css class

Thanks for that bit of info, wasn't aware of it!

[Moo] Re: how to filter elements by css class

you should be able to filter out the main selector results like this: var all = $$('ul.menu li'), filtered = all.filter('li:not(.parent,.active,.item33,.item34,.item35)') ; http://jsfiddle.net/subhaze/jeYZT/

[Moo] Re: mootools core/more build.rb troubles

worked like a charm, thanks man!

[Moo] mootools core/more build.rb troubles

I was wondering if anyone is successfully using the build.rb file that comes with the mootools git repos. I have it forked and cloned on my local system, but when i run it for more i get "./assets/core/Soure/ scripts" is an invalid directory. For core, nothing happens. I use this: ruby build.rb t