-
Notifications
You must be signed in to change notification settings - Fork 200
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
Bikeshed output fails Specberus validation for WD #802
Comments
Fixed now. (This was something that had to be handled by an extension script in your
I'll see if I can get this unflagged as a problem. Ignore for now.
Hmm, this must be a new requirement. I'll investigate and see if I need to do anything or if it should be rolled back.
There are lots of elements without end tags in a Bikeshed document, as it omits all the omittable end tags on purpose. ^_^
|
I just pulled down the latest bikeshed and this appears to still be broken for me. I ran Bikeshed on the spec and the W3C stylesheet was still before the local CSS. Then I noticed that the code change puts this new processing in an if prepTR, so I tried adding "Prepare for Tr: true" to the metadata. That led to this error (I've changed the Windows style slashes to the Unix style so they show up better in the comment): Traceback (most recent call last): |
Ah darn, that's what I get for not actually testing the code. Fixed, sorry.
As you found, these fixups are gated by the |
Thanks, works now. |
I hit this when trying to publish https://www.w3.org/TR/2016/WD-webauthn-20160902/ through Echidna.
Error (fatal):
Warnings (not fatal but easily fixed):
Aesthetic (not flagged but it bothered me):
The text was updated successfully, but these errors were encountered: