bahman2000,
thanks for the feedback. This is a know (at least by me

) problem with 1.0. The primary focus of 1.1 is to resolve issue around reporting of status and what appears to be a bug in firefox which cause the 'no such channel' error.
FYI the 'no such channel' error occurs when you are running more than one tab or firefox window. Firefox appears to send ajax status information to the wrong instance of noojee click. Noojee Click 1.1 is being re-written to use the new module facility in firefox to work around this bug. The issue with the status message hanging around is just my poor coding
