I'm seeing some strange behaviour which took a while to get to the bottom of. Basically a script file that I once had in my widget is still available. Though I deleted the file, I accidentally left the including <script> in, and after tearing my hear out with some really bizarre behaviour it seems the file still exists as far as the client is concerned.
I've checked it's not in the .wgt that gets deployed yet the browser sees it. So there must be some caching someplace causing this. My guess this would be quite late in the chain, for example when the widget is deployed to Apache as separate files. The solution is no doubt to delete all content in the target dir widget before copying the widget files. Trust me to find a edge case. Steve Lee Programme Leader (Open Accessibility) OpenDirective http://opendirective.com
