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!
![5 HTML5 APIs You Didn’t Know Existed]()
When you say or read "HTML5", you half expect exotic dancers and unicorns to walk into the room to the tune of "I'm Sexy and I Know It." Can you blame us though? We watched the fundamental APIs stagnate for so long that a basic feature...
![5 Ways that CSS and JavaScript Interact That You May Not Know About]()
CSS and JavaScript: the lines seemingly get blurred by each browser release. They have always done a very different job but in the end they are both front-end technologies so they need do need to work closely. We have our .js files and our .css, but...
![AJAX Username Availability Checker Using MooTools]()
![Create a Sprited Navigation Menu Using CSS and MooTools]()
CSS sprites are all the rage these days. And why shouldn't be? They're easy to implement, have great upside, and usually take little effort to create. Dave Shea wrote an epic CSS sprites navigation post titled CSS Sprites2 - It's JavaScript Time.
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