search

w3c / webappsec-secure-contexts

WebAppSec Secure Contexts
https://w3c.github.io/webappsec-secure-contexts/
Other
33 stars 38 forks source link

Add Status section #92

Closed sideshowbarker closed 2 years ago

sideshowbarker commented 2 years ago

This needs be moved to the boilerplate section of the Bikeshed repo; but adding it here now in the interest of un-blocking the Geolocation spec transition.

sideshowbarker commented 2 years ago

@xfq After merging, autopublishing to TR seems to be failing with the same errors:

https://github.com/w3c/webappsec-secure-contexts/runs/3532134463#step:3:555

Since I’ve not gotten the boilerplate into the Bikeshed repo yet, I overrode it and put the status paragraphs into the source directly. And that works fine locally. But maybe not with spec-prod?

sideshowbarker commented 2 years ago

@sidvishnoi, @deniak, @marcoscaceres do you have any ideas why autopublishing to TR from the repo is failing — despite the fact the Status content that specberus is looking for is in fact in the spec?

The failures are at https://github.com/w3c/webappsec-secure-contexts/runs/3542602328#step:3:557

https://w3c.github.io/webappsec-secure-contexts/#status is the ED with the Status section included

marcoscaceres commented 2 years ago

Could it be that it's not wrapped in a <section id="sotd">?

marcoscaceres commented 2 years ago

Hmm... maybe not...

deniak commented 2 years ago

I think the issue comes from the fact that the whole TOC comes between the <h2>Status of this Document</h2> and all the paragraphs that section.

deniak commented 2 years ago

I'm not super familiar with bikeshed but the source document seems to be missing some closing </p>

sidvishnoi commented 2 years ago

To ease in debugging, I've added support for build artifacts in spec-prod (https://github.com/w3c/spec-prod/pull/102). Running the action now (in PR as well as merge) will create an artifact with name spec-prod-result containing output of the build which can be downloaded and inspected locally.