handling URLs that start with "//xyzw...."

When i started running my app in a production environment, some assets like images started to show up as "url": "//xyz...".

My app is using a Rails back-end and it uses cloudfront in a vanilla way, so I think you may face this in the future. So, it may be a good thing to support url schemes like this, since I believe they are standard. I am not sure if you process the data at this level before rendering, in which case, it may be easy for you to handle it the way a regular web browser would.

The issue names no files or tests. Start by locating the URL parsing and rendering entry point, then reproduce an asset URL beginning with "//"; done means the app handles that protocol-relative URL consistently with the expected browser behavior.

Written by the indexing model from the issue text.