> Using comments to wrap something that you want to keep in the document > is a bad idea. Sure, it might happen to work with Kid, but I still > wouldn't do it or recommend it.
That technique has been recommended for JS since day 1. It's the standard way of hiding JS from non-javascript-aware browser. You wrap it in a comment so if your user agent doesn't understand JS, it doesn't go printing it everywhere. Not that you should be putting JS in your <body/> though. I'm fine with JS on-page when it only affects that page. Including it in a global JS file increases bandwidth. Including it in its own external file causes connection overhead (in HTTP/1.0) > -bob -Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
