Quote Originally Posted by dbltoe View Post
Whether a src for an image, a script, and iframe or simply a source -- a double slash following the src=" violates the whole src attribute syntax and will cause many hours of hair-pulling searches for the problem. The browser would assume it is relative but would be looking for yourSite.com//someFile. Can you say, "Fill the log file?"
The same applies to the new <source> tag in html5.

Thus, the NEVER.
No, it would not look for Your-site dot com//something, it would look for http: // Your-site dot com or https: // Your-site dot com if the information that followed // was Your-site dot com. Ie.

Src="// Chosen-site dot com/foldername/file.jpg

If the current uri were: http :// Mysite dot com/index.php?main_page=product_info&cPath=5&products_id=47

Then the image would be pulled as http :// Chosen-site dot com/foldername/file.jpg

But if the current uri were: https : // Mysite dot com/index.php?min_page=login

Then the image would be pulled as https :// Chosen-site dot com/foldername/file.jpg

Again the http: or https: applicable to the served page would be prepended with the content that includes and follows the //.