Open source and web accessibility evangelist, front-end engineer, destigmatizing mental illness, podcaster, writer, speaker, and devrel. I want to make a meaningful impact no matter how small.
I'm a web developer, graphic designer, type designer, musician, comicbook-geek, LEGO-collector, food lover … as well as husband and father, located just south of Copenhagen, Denmark.
I just tested in the latest versions of Chrome and Canary (MacOS) – they both have the ping-attribute, when performing and inspecting the markup for a Google Search. I then clicked preserve log to test the ping – and it's still being transmitted:
Open source and web accessibility evangelist, front-end engineer, destigmatizing mental illness, podcaster, writer, speaker, and devrel. I want to make a meaningful impact no matter how small.
Tried it again with a different profile in Chrome and it works. 🤷♂️ I have no idea what is different between the profiles also, I surely have a different profile in Canary?
I thought it might be Privacy Badger, but nope. Bizare. Alas, I believe the conclusion is that it does work by default in Chrome.
I'm a web developer, graphic designer, type designer, musician, comicbook-geek, LEGO-collector, food lover … as well as husband and father, located just south of Copenhagen, Denmark.
Open source and web accessibility evangelist, front-end engineer, destigmatizing mental illness, podcaster, writer, speaker, and devrel. I want to make a meaningful impact no matter how small.
Tested with Chrome 90.0.4430.85 (Official Build) (x86_64) as well as Canary (~92). Works out of the box with Safari and Edge as well as with Firefox if I toggle the flag.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Interestingly, I think Google might have turned this off as well now. See github.com/mdn/browser-compat-data...
I just tested in the latest versions of Chrome and Canary (MacOS) – they both have the
ping
-attribute, when performing and inspecting the markup for a Google Search. I then clickedpreserve log
to test theping
– and it's still being transmitted:Tried it again with a different profile in Chrome and it works. 🤷♂️ I have no idea what is different between the profiles also, I surely have a different profile in Canary?
I thought it might be Privacy Badger, but nope. Bizare. Alas, I believe the conclusion is that it does work by default in Chrome.
Yes, at least for now. One could hope that Chrome would either remove it, or at least notify the user, as the specs states.
Huh, how strange. I wonder if it is the way I am testing it with this sample app:
github.com/schalkneethling/using-p...
and specifically:
github.com/schalkneethling/using-p...
Tested with Chrome 90.0.4430.85 (Official Build) (x86_64) as well as Canary (~92). Works out of the box with Safari and Edge as well as with Firefox if I toggle the flag.