Server-Side Rendered Page Fails W3C Check

[nelsonic]

W3C check is failing on the custom elements:

[nelsonic]

Without the custom tags the page validates fine:
https://validator.w3.org/nu/?doc=http%3A%2F%2Fpurecss.io%2Flayouts%2Fblog%2F

[iteles]

I also tried an example using riot-tag attributes in the HTML instead of custom tags but this also failed the validator. 😞

[iteles]

I do find it odd however that even though it's not standards compliant, it doesn't fail accessibility checkers like tenon.io or WAVE.

[gregorypratt]

FYI riot/riot#1342 (comment)

[iteles]

@gregorypratt 👍 Looking forward to seeing where this goes!

[aMarCruz]

@nelsonic , @iteles If we could render something as

<div data-riot-tag="page-head">
</div>

...the problem would be solved. Right?
Perhaps this can be done without overgrow the riot core.

[nelsonic]

@aMarCruz yeah, that could solve the issue...

[aMarCruz]

@nelsonic In ~2-3 weeks I will submit a PR for the upcoming riot v3.0 trying to fix this issue.

[nelsonic]

@aMarCruz that will be amazing! 👍
You should have write access to this repo (I just invited you...)

[aMarCruz]

@nelsonic thanks! just now I'm involved in a medium-sized private project, would not have the time to collaborate as I wanted, but in the future for sure.
I'll post here when the PR is ready.