There were some issues with external javascript files (like MooTools) that had // that weren’t comments. MooTools has a few occurrences of // within the code (as do some other libraries) that weren’t comments, but were being treated as comments. This was causing all sorts of problems.
For example, the following code works fine as an external javascript file:
?el.4N.3g(\‘9Y://\’,\’\’)
But when it’s inline, everything after the // is commented out. The fix is to make it look like this:
?el.4N.3g(\‘9Y:\/\/\’,\’\’)
This gets tricky because you don’t want to escape out real comments. We’ve tried to work around this by only converting // to \/\/ when it is not prefixed with spaces and/or a line break. So…
// <— These won’t get converted, because they’re at the beginning of a line. var foo = ‘//’; <—// These will get converted to ‘\/\/’, since they’re not preceeded by a space. var foo = ‘ //’; <--// These will not get converted. They’re preceded by a space. var foo = ‘bar’; // A comment goes here <— These won’t get converted either.
Make sense? It’s not perfect, but it’s a start. Let us know what you think.
This one is pretty simple. We’re replacing all http://www.google-analytics.com/urchin.js script calls with https://ssl.google-analytics.com/urchin.js. Just a little convenient improvement so you don’t have to worry about rewriting your Google Analytics script calls.
Love it? Hate it? Have questions or comments? Let us know!