Listen for the Delete Key Using MooTools
I saw an interesting ticket hit the MooTools Lighthouse system recently. A user reported that they could not use the following code snippet to listen for the delete key:
var isdel = Event.Keys.delete;
While that generally works, it does not work for the delete key because "delete" is a reserved word. Instead, you must listen for the delete key with this code snippet:
var isdel = Event.Keys['delete'];
Very interesting. As flexible as Moo's language is, you can't get around the reserved words!
![JavaScript Promise API]()
While synchronous code is easier to follow and debug, async is generally better for performance and flexibility. Why "hold up the show" when you can trigger numerous requests at once and then handle them when each is ready? Promises are becoming a big part of the JavaScript world...
![Create a CSS Cube]()
CSS cubes really showcase what CSS has become over the years, evolving from simple color and dimension directives to a language capable of creating deep, creative visuals. Add animation and you've got something really neat. Unfortunately each CSS cube tutorial I've read is a bit...
![Modal-Style Text Selection with Fokus]()
Every once in a while I find a tiny JavaScript library that does something very specific, very well. My latest find, Fokus, is a utility that listens for text selection within the page, and when such an event occurs, shows a beautiful modal dialog in...
![AJAX Username Availability Checker Using MooTools 1.2]()
mootools rules! :)
Thanks for keeping us informed, David!
So did you let them know about your solution? :D
Or did they already take care of that in the docs?
(not to sound like a jack*ss, of course, just curious)