This is definitely not the case, the team behind Pik is eager to get JPEG XL deployed, but Chrome is blocking it.
I'm not sure what we are misunderstanding from each other. I'm saying google could very well be blocking it's deployment in chrome because it is not the implementation they originally came forward with if they are that petty and NIH.
The team that wrote the original Google proposal (PIK) joined forces with the team that wrote FUIF and together they created JXL, so no, those particular Googlers are not petty about this.
They're a distinct team from the Chrome team though.
While that's a possibility the article made it seem like Google's PIK team and Cloudinary worked together on JPEGXL
Same with av1. It's not verbatim vp10, but incorporates concepts developed by xiph.org and Cisco (and whoever else).