I could agree about all objections. But, as I wrote at the begging of article and its very end, this is just one of many possible solutions and it’s unfinished. By writing this code, I wanted to present how jQuery can help in spearation of presentaion layer from business logic.
Therefore, in that context, is HTML well formed or is it packed as plug-in or not, is not that relevant. Of course, it would be better if I haven’t used “bogus” attributes or code encapsulated as jQuery plug-in. But that would only make JS developers happier, not contribute to subject of analyse.

Talking about “bogus” attritube. Idea behind this was to a) leave ID and CLASS attribute free to designers to play with by their own will and, at the same time, B) to provide additional info to jQ selector to locate element(s) faster.

So, if I ever decide to further develop this code, I’ll have your words in mind.
Thank you for your comment.

No plugin, no API, no options? How does this help when there are multiple other jquery based menus that are easy to set up, and have those attributes.

What about hover Intent compatibilty?

Finally, adding non valid code with a bogus attribute “ctt” is just plain wrong!