Skip to content
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

Fix itemprop errors from w3c validator in jinja themes #2994

Merged

Conversation

edwinsteele
Copy link
Contributor

https://validator.w3c.org flags itemprop attributes as an error
on any element that specifies them unless the itemtype attribute
in a parent element references a valid schema. The validation
error is:

"Error: the itemprop attribute was specified but the element is
not a property of any item"

This change fixes the validation error.

Pull Request Checklist

  • [/] I’ve read the guidelines for contributing.
  • [/] I updated AUTHORS.txt and CHANGES.txt (if the change is non-trivial) and documentation (if applicable).
  • [/] I tested my changes.

Description

https://validator.w3c.org flags itemprop attributes as an error
on any element that specifies them unless the itemtype attribute
in a parent element references a valid schema. The validation
error is:

"Error: the itemprop attribute was specified but the element is
 not a property of any item"

This change fixes the validation error.
@ralsina
Copy link
Member

ralsina commented Mar 21, 2018

The -jinja themes are autogenerated using scripts/jinjify from their mako siblings.

Could you make the same change in base instead of base-jinja and then run jinjify?

If not, I can do it.

@Kwpolska
Copy link
Member

I can see the change in both versions.

Copy link
Member

@Kwpolska Kwpolska left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ralsina ralsina merged commit 3fe69a4 into getnikola:master Mar 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants