Morning!
I added the following line of code to disable the skype feature on phone numbers.
<meta name="SKYPE_TOOLBAR" content="SKYPE_TOOLBAR_PARSER_COMPATIBLE" />
The problem is that it is causing the following error.
Line 6, Column 71: Bad value SKYPE_TOOLBAR for attribute name on element meta: Keyword skype_toolbar is not registered.
Syntax of metadata name:
A metadata name listed in the HTML specification or listed in the WHATWG wiki. You can register metadata names on the WHATWG wiki yourself.
Is there a work around for this? I need to ensure that the skype numbering doesn't take over the phone numbers but also validate at the same time.
Thanks for reading.
You can submit a metadata registration to the WHATWG wiki as instructed, or you can ignore the error message. Neither of these has any effect on whether your page works as intended.
Use HTML 4.01 (which lacks the HTML 5 draft's bizarre limits on what constitutes valid meta data).
Related
Since HTML 5, the rel="" attribute (for "Link types") no-longer accepts "first" and "last" as valid values. These keywords are meant to represent the first and last pages in a page sequence, however only "prev" and "next" are supported:
https://developer.mozilla.org/en-US/docs/Web/HTML/Link_types
first - Indicates that the hyperlink leads to the first resource of the sequence the current page is in. This is an obsolete API and is no longer guaranteed to work.
last - Indicates that the hyperlink leads to the last resource of the sequence the current page is in. This is an obsolete API and is no longer guaranteed to work.
next - Indicates that the hyperlink leads to the next resource of the sequence the current page is in.
prev - Indicates that the hyperlink leads to the preceding resource of the sequence the current page is in.
Curiously, the HTML 4.01 specification (December 1999) does list "Start" as a valid value - this value does not appear in the HTML5 specification nor Mozilla's MDN page: https://www.w3.org/TR/html401/types.html#type-links
Start - Refers to the first document in a collection of documents. This link type tells search engines which document is considered by the author to be the starting point of the collection.
Going back further in time, the HTML 3.2 specification (January 1997) does not suggest any "first" or "last" equivalents, only next and previous ( https://www.w3.org/TR/REC-html32#anchor ).
Does anybody know of a valid alternative for rel values first/last, or should I just carry on using them just in case Google or other search engines still care to understand them?
These values were deprecated because they were used rarely and inconsistently. Only a couple of user agents did anything interesting with these values, and many validators did not even check them.
I don't agree with the rationale for deprecating these (because rel may be used for internal anchors too), but I suppose it is a lost cause.
So to answer your question, there is no 'standard' alternative. If you need to add this information to your site, I suggest using a data- attribute instead. For example:
<link data-rel="first" href="slide01.html />
<link data-rel="last" href="slide999.html />
There is a javascript API for accessing these values, and it's valid HTML5. Just don't expect the browser to pay much attention to them.
The whole point of data attributes is to insert whatever data you (as page author/developer) need to associate with a given element. You might ask yourself why you want to add this data, and (more importantly) who/what will consume this data.
The Google+ JS API shows credentials and settings can be set using meta tags instead of passing through a JS call. Examples:
<meta name="google-signin-clientid" content="CLIENT_ID" />
<meta name="google-signin-cookiepolicy" content="single_host_origin" />
I tried this on my website and it works, but when I try to
validate my HTML the validator gives errors such as:
Bad value google-signin-callback for attribute name on element meta:
Keyword google-signin-callback is not registered.
Bad value google-signin-clientid for attribute name on element meta:
Keyword google-signin-clientid is not registered.
Bad value google-signin-cookiepolicy for attribute name on element
meta: Keyword google-signin-cookiepolicy is not registered.
Bad value google-signin-scope for attribute name on element meta:
Keyword google-signin-scope is not registered.
Is the HTML code Google provides as an example really invalid?
You are validating against HTML5 (this can be seen from the error messages), and as per HTML5 drafts, only a limited set of name attribute values are allowed in a meta element. So as an HTML5 document, the document is invalid, since the values used are among those allowed. HTML5 defines a registration procedure, but apparently Google cannot be bothered to use it.
If you validate against XHTML 1.0, the code will pass, because in XHTML 1.0, the name attribute value can be any name, like <meta name="Hi, I’m trying to make a point” content="" />. The same applies to HTML 4.01, except that the slash before “/” would cause a syntax error in it.
It's valid HTML, the names being used are not part of the official standard. That's fine though since they are namespaced with google so you shouldn't have any issues.
I am getting the above validation error in response to the following line in my HTML:
<meta http-equiv="X-XRDS-Location" content="http://www.example.com/wp-content/plugins/socialauth-wp/hybridauth/index.php?get=openid_xrds" />
I use WordPress social auth plugin, that automatically adds this line to the head of every page.
I am not sure what this line does to the site but it throws a validation error.
What does the meta line does to the site, is it mandatory?
I gone through the question
Get rid of “Bad value X-XRDS-Location for attribute http-equiv on XHTML element meta.” in XHTML5 validation, but I'm not sure how to register it.
My answer to the linked question applies here, too:
If you use HTML5, you may only use the following values for the http-equiv attribute:
those defined in the HTML5 spec, or
those registered in the WHATWG wiki page "PragmaExtensions".
X-XRDS-Location is not defined/registered, so HTML5 doesn’t allow to use it.
What does the meta line does to the site, is it mandatory?
I guess the linked XRDS document is used to discover your OpenID service provider. Or for Oauth, etc..
An alternative may be to send the HTTP header X-XRDS-Location. If you send it, you could remove the meta element (unless some data consumers only look for the occurence in the HTML, which would be a bad practice).
I'm using mobile template HTML files on a PHPBB forum.
I tested the html for errors at http://validator.w3.org/
The test results showed the following error
Line 24, Column 66: {navlinks.FORUM_NAME}
Bad value up for attribute rel on element a: The string up is not a registered keyword or absolute URL.
Not having heard back from the author and not finding much on Google search, I'm trying to understrand what rel="up" does, if anything constructive.
Can't find any mention as an official HTML attribute
http://www.w3schools.com/tags/att_link_rel.asp
wondering if it's probably safe to just remove the phrase rel="up"
The Internet Assigned Numbers Authority (IANA) keeps a list of link relationships The latest version is from March 21 2013.
up: Refers to a parent document in a hierarchy of documents.
Unfortunately, despite the fact that this registry was long established, it was decided that HTML5 would not use this registry and would use a Wiki page to list the conforming link types instead.
Up, is listed in a rather insane section marked "dropped without prejudice", which nobody seems to know what to do with, or how to get those link types out of.
It's safe to drop it, but some browsers and browser plugins make use of it. For example, I use a Firefox plugin called "Link Widgets" like this to make use of the link type.
From: http://www.w3.org/MarkUp/html3/dochead.html
REL=Up
When the document forms part of a hierarchy, this link references the immediate parent of the current document.
If this is causing any specific problems or unexpected results, please post your code. Thanks.
Wordpress generates category links with a rel="category" attribute. When I run my site through w3c.org's validator, it tells me that this is invalid, and that I can register link types on the Microformats wiki (http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions). However,
Is this a problem with the validator, or am I doing something incorrectly? Thanks in advance.
The rel value "category" is not invalid. Instead, the validator is not up to date.
category is registered officially in the microformats.org wiki page.
So it's no problem to use this value. The validator will probably catch up in the future.