@doctype_jon it's a bit confusing as the issue started out as a mention of Chrome aligning to MobileSafari's behavior (which landed in Chrome 108), but then got transformed into a request about supporting the meta tag extension.