-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Aryeh Gregor wrote:
On Mon, Sep 8, 2008 at 3:04 PM, Gregory Maxwell
<gmaxwell(a)gmail.com> wrote:
On this subject, as part of the IPv6 testing
I've run a JS tester on
ENWP for a couple of months now which has determined that for hosts
able to run the JS tester, protocol relative urls (i.e. <img
src="//upload.wikimedia.org/foo.jpg"/>) work for all clients.
If protocol relatives turn out to be universally supported they would
remove one problem from doing a native SSL deployment.
Why would one suspect that they're not universally supported?
It's the kind of weird, uncommon thing that just screams "I'm a corner
case that lots of people probably didn't bother to implement because I'm
not in common use in the wild". :)
Even if browsers support it I would expect to see a lot of bots and
spiders choke on it -- it's bad enough a lot don't understand that
"&" in an <a href="..."> needs to be decoded as
"&"... :)
- -- brion
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org
iEYEARECAAYFAkjFqJ4ACgkQwRnhpk1wk46SHQCgwWEP9SffsC9TkJDSfsc95B3v
YGwAn3Y++xiG0Hlxt6wxyUOZeChLz2Ly
=4Jco
-----END PGP SIGNATURE-----