Bug 987 – google-translate-customization unecognized

NOTE: The current preferred location for bug reports is the GitHub issue tracker.

Bug 987 - google-translate-customization unecognized


Summary:	google-translate-customization unecognized

Status:	RESOLVED INTENTIONAL

Product:	Validator.nu
Classification:	Unclassified
Component:	General
Version:	HEAD
Hardware:	All All

Importance:	P2 minor
Assigned To:	Nobody

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-02-22 03:12 CET by MikeP
Modified:	2014-02-22 08:44 CET (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description MikeP 2014-02-22 03:12:39 CET

The Meta tag google-translate-customization returns an error even though it is registered.

Error returned is:

Error: Bad value google-translate-customization for attribute name on element meta: Keyword google-translate-customization is not registered.
From line 40, column 1; to line 40, column 111
a Tag -->↩<meta name="google-translate-customization" content="xxxx" />↩↩<!--
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.

Comment 1 Michael[tm] Smith 2014-02-22 08:43:36 CET

google-translate-customization doesn't meet the registration requirements in the spec, due the fact that Google doesn't actually provide any documentation that defines what it means.

The https://support.google.com/translate/?hl=en page that the wiki entry linked to doesn't mention google-translate-customization at all.

So I've moved google-translate-customization to the "Proposals that don't meet the requirements for a registration" section of the wiki page http://wiki.whatwg.org/wiki/MetaExtensions#Proposals_that_don.27t_meet_the_requirements_for_a_registration