I like this. Hate his non xhtml-strict compliant markup (old school).
This is a very creative way to tackle a problem and I love the fact that his JS doesn't add any elements to the existing markup. I feel that once your JS starts drawing dom elements, you've messed up somewhere (unless your front-end is completely JS, different topic). There are of course cases where it is necessary -- supporting older browsers or shimming functionality -- but I've grown to love the separation of markup and interaction.
One could probably build on this idea (wrap your favorite lib) and do things like:
'clicking on ".selector" sends post ".selector[:href]" ..."
But that may make things a bit more complicated in the long run.
Either way, should be fun seeing the 2048-ification of this in the upcoming weeks
Comments
I like this. Hate his non xhtml-strict compliant markup (old school).
This is a very creative way to tackle a problem and I love the fact that his JS doesn't add any elements to the existing markup. I feel that once your JS starts drawing dom elements, you've messed up somewhere (unless your front-end is completely JS, different topic). There are of course cases where it is necessary -- supporting older browsers or shimming functionality -- but I've grown to love the separation of markup and interaction.
One could probably build on this idea (wrap your favorite lib) and do things like:
'clicking on ".selector" sends post ".selector[:href]" ..."
But that may make things a bit more complicated in the long run.
Either way, should be fun seeing the 2048-ification of this in the upcoming weeks