Implement MooTools Element.getSiblings()
Update: I've added the "match" option to the getSiblings() method.
While browsing through the open tickets at the MooTools LightHouse, I found this little gem proposed by SixtyMonkey:
Element.implement({
getSiblings: function(match,nocache) {
return this.getParent().getChildren(match,nocache).erase(this);
}
});
The above code grabs all sibling elements (the collection of alike elements minus the "found" one.) Do you think this should be added to the core?
I submitted this to core and it has been accepted. Look forward to seeing this in core!
![CSS Animations Between Media Queries]()
CSS animations are right up there with sliced bread. CSS animations are efficient because they can be hardware accelerated, they require no JavaScript overhead, and they are composed of very little CSS code. Quite often we add CSS transforms to elements via CSS during...
![Create Namespaced Classes with MooTools]()
MooTools has always gotten a bit of grief for not inherently using and standardizing namespaced-based JavaScript classes like the Dojo Toolkit does. Many developers create their classes as globals which is generally frowned up. I mostly disagree with that stance, but each to their own. In any event...
![Dress Up Your Select Elements with FauxSelect]()
I received an email from Ben Delaney a few weeks back about an interesting MooTools script he had written. His script was called FauxSelect and took a list of elements (UL / LI) and transformed it into a beautiful Mac-like SELECT element.
![GitHub-Style Sliding Links]()
GitHub seems to change a lot but not really change at all, if that makes any sense; the updates come often but are always fairly small. I spotted one of the most recent updates on the pull request page. Links to long branch...
hello david!
i was wondering when this method would becomes part of the core? in MooTools 2 perhaps? or would you guys do something like MooTools 1.2.4 or something?
It is – just not documented
little typo
nocash -> nocache