-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AMP with Blogger - The header with xmlns #760
Comments
Can you post to StackOverflow with the "amp-html" tag and I'll answer there? Thanks! |
I don't have any response about this... someone could help? |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When i try to use the AMP specification with my Blogger's code i have found some errors in my console with the development mode activated: ´´´<script async='true' src='https://cdn.ampproject.org/v0.js' development='true'></script>´´´ :
AMP validation had errors:
validator.js:154 http://www.diariosdelanube.com/:1:0 DISALLOWED_ATTR xmlns (see https://github.com/ampproject/amphtml/blob/master/spec/amp-html-format.md#ampd)validator.js:154 qd.error
I have seen the referenced link to know how i have to build my "header", and i have a lot of DISALLOWED_ATTR because the Blogger's nature of my code. what can i do to do it "AMP compliance"?:
For example, this is my "header definition" in Blogger:
PROBLEM Nº1) The "HTML" header:
The
xmlns='http://www.w3.org/1999/xhtml'
attribute it's not admited by the validator.js. I have to change all the html header with this to pass the validator:I have to add
amp=' '
because the Blogger's code validator doesn't allow me to add<html amp>
or<html ⚡>
top level tag. And If i add theamp=' '
in my html top level tag i get this error in the amp's validator:http://www.diariosdelanube.com/:1:0 DISALLOWED_ATTR amp validator.js:154 qd.error
is it possible to use amp code with the blogger's specification?
What can i do to it well?
Thank you very much!!!
The text was updated successfully, but these errors were encountered: