Whilst doing accessibility and compliance checks I hit an issue with the our FarCry sites and the use of meta
name="inheadid". The site is failing checks with the following error:
Bad value 'inheadid' for attribute 'name'. Meta name 'inheadid' is not registered.
I’ve done some research and found that HTML changed the rules for the meta tag:
You can now only use the standard set of names otherwise you need to have your name registered as an extension value. Details are here: https://wiki.whatwg.org/wiki/MetaExtensions
Will Daemon request the
inheadid be registered or suggest an alternative existing meta name to be used? From what I can see, the
inheadid is heavily used in FarCry.
Core generates the
META tag to assist with dynamically updating a page with JS when the source changes.
26 <cfset st = structnew() />
27 <cfset st["id"] = "inhead-#request.inHead.aCustomIDs[i]#" />
28: <cfset st["html"] = chr(13) & '<meta id="inhead-#request.inHead.aCustomIDs[i]#" name="inheadid" content="#request.inHead.aCustomIDs[i]#">' & request.inHead.stCustom[request.inHead.aCustomIDs[i]]>
29 <cfset arrayappend(aResult,st) />
This generates one or more of these in the
<meta id="inhead-943DB1A0-CEAE-11E4-AA6A005056A670CB" name="inheadid" content="943DB1A0-CEAE-11E4-AA6A005056A670CB">
There’s no particular reason for calling it
inheadid – we just need to find a suitable alternative.
Sounds like a good match. Also much easier to use an existing one rather than trying to get one registered
I’ve opted for using the
property attribute on
<meta> instead of the
name attribute which should be fine going forward for HTML5 doctypes. This is fixed in p710