FF and img rendering

colak · 2018-05-19 17:25:38

On FF many img tags do not load properly as the platforms link to them by omitting the http(s) part… The cargo collective platform is one of them.
This page for example loads the image in all my other browsers but FF.

I also noticed similar kind of linking with javascript… ie <script src="//site.tld/js/script.js"></script>. Could somebody shed a light on this? W3 validator accepts this method but not FF.

gaekwad · 2018-05-19 19:27:22

colak wrote #311897:

This page for example loads the image in all my other browsers but FF.

Hmm – seems OK here, you want screenshots of what I can see here on Firefox Quantum?

michaelkpate · 2018-05-19 20:35:34

colak wrote #311897:

On FF many img tags do not load properly as the platforms link to them by omitting the http(s) part… The cargo collective platform is one of them.

I just checked with FF 59 on Ubuntu. Works fine for me.

phiw13 · 2018-05-20 00:32:31

colak wrote #311897:

On FF many img tags do not load properly as the platforms link to them by omitting the http(s) part… The cargo collective platform is one of them.
This page for example loads the image in all my other browsers but FF.

I also noticed similar kind of linking with javascript… ie <script src="//site.tld/js/script.js"></script>. Could somebody shed a light on this? W3 validator accepts this method but not FF.

Weird. As others have mentioned, the images load for me on that site (and I often uses that syntax without problem).

Check the browser console to see if it throws any message; perhaps a plugin/extension is interfering with that page?

colak · 2018-05-20 07:15:37

Hmmm, I did check the console which prompted me to also check my about:config which is where I blocked such urls, as I read some time ago that they posed some security issues…

jakob · 2018-05-20 10:30:15

FWIW: the links are fine for me too on FF.

colak wrote #311907:

Hmmm, I did check the console which prompted me to also check my about:config which is where I blocked such urls, as I read some time ago that they posed some security issues…

AFAIK the main reason for //… links is so that the links function correctly on http:// and https:// without needing correction. The only ‘problem’ I’ve had with them, is that when run locally from an .html file, they produce file://… links instead of http://… links. Not sure about the security issues.

Textpattern CMS

Textpattern CMS support forum

#1 2018-05-19 17:25:38