This still buries the lede a mile deep — it does not cover the other issue, which is that Chrome randomly™ decided to start auto-filling this field in the current version. Never happened with older versions.
Has nothing to do with the metadata. This field was never auto filled in the past. Then suddenly it was.