The current version of the jscookMenu tag [R292680, 2005-10-13] now throws an exception, with message:
"You provided a wrong themeName.".
I see that new features have been added to support custom themes. This is fine, but please restore the original behaviour of accepting an unknown themeName value. A bump in the "patch-level" release number (1.1.0 -> 1.1.1) should not have changes that break valid existing user code.
The problem change is to class
Possibly a warning (logged or even output as a js comment) could be generated by the jscookMenu code to recommend to people that they modify their pages to use the new custom-theming attributes, but throwing an exception isn't nice.
This has been discussed on the user email list: