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 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...
![fetch API]()
One of the worst kept secrets about AJAX on the web is that the underlying API for it, XMLHttpRequest, wasn't really made for what we've been using it for. We've done well to create elegant APIs around XHR but we know we can do better. Our effort to...
![jQuery Link Nudge Plugin]()
A while back I debuted a tasteful mouseover/mouseout technique called link nudging. It started with a MooTools version and shortly thereafter a jQuery version. Just recently Drew Douglass premiered a jQuery plugin that aimed at producing the same type of effect.
![Page Visibility API]()
One event that's always been lacking within the document is a signal for when the user is looking at a given tab, or another tab. When does the user switch off our site to look at something else? When do they come back?
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