This bug is about the MooTools framework, specifically about the Element.getElementById() method.
The docs indicate:
Synopsis: Gets the element with the specified id found inside the current Element.
Example: var myChild = $('myParent').getElementById('myChild');
Notes: This method is not provided for Document instances as document.getElementById is provided natively.
Did you spot it? No? Lets run through it bit by bit.
For starters MooTools uses a very simple $('someID') syntax to get an element by its ID.
Combine that with the fact that the ID attribute of HTML elements must be unique within the document according to the W3C specs... and you've now proven that the .getElementById() method on any other element in the DOM is redundant.
E.g. the above example can also be written as (and in much less code I might add):
Example: var myChild = $('myChild');
Now maybe I'm missing something here that is hidden in the docs that helps explain why verbose, redundant code is somehow helpful or that it provides additional features? If so, please comment and let me know!
Known Workarounds: One. Simply don't use it! Its too bad that the API is cluttered with this extra method but it won't cause any harm to use it.
Example Workaround Code:
var myChild = $('myChild');
Related Issues: None.
Submit a bug