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.

Sign up for GitHub

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

Jump to bottom

Respec warnings related to missing <dfn> and Object error #978

Closed
vivienlacourba opened this issue Dec 20, 2016 · 5 comments
Closed

Respec warnings related to missing <dfn> and Object error #978

vivienlacourba opened this issue Dec 20, 2016 · 5 comments
Labels
Editorial PR exists

Comments

@vivienlacourba
Copy link
Member

I noticed some respec warnings while running:
cd webrtc-pc && git checkout master && git pull
make clean && make update && make check

...
node support/respec/tools/respec2html.js -e --src file://`pwd`/webrtc.html --out build/output.html
🚨 ReSpec warn: No <dfn> for rtcconfiguration.
🚨 ReSpec warn: No <dfn> for rtcicecredentialtype.
🚨 ReSpec warn: No <dfn> for rtciceserver.
🚨 ReSpec warn: No <dfn> for rtcicetransportpolicy.
🚨 ReSpec warn: No <dfn> for rtcbundlepolicy.
🚨 ReSpec warn: No <dfn> for rtcrtcpmuxpolicy.
🚨 ReSpec warn: No <dfn> for rtcofferansweroptions.
🚨 ReSpec warn: No <dfn> for rtcofferoptions.
🚨 ReSpec warn: No <dfn> for rtcansweroptions.
🚨 ReSpec warn: No <dfn> for addicecandidate!overload-1 in rtcpeerconnection.
🚨 ReSpec warn: No <dfn> for rtcsignalingstate.
🚨 ReSpec warn: No <dfn> for rtcicegatheringstate.
🚨 ReSpec warn: No <dfn> for rtcpeerconnectionstate.
🚨 ReSpec warn: No <dfn> for rtciceconnectionstate.
🚨 ReSpec warn: No <dfn> for rtcpeerconnectionerrorcallback.
🚨 ReSpec warn: No <dfn> for rtcsessiondescriptioncallback.
🚨 ReSpec warn: No <dfn> for rtcstatscallback.
🚨 ReSpec warn: No <dfn> for rtcsdptype.
😱 ReSpec error: [object Object]
@aboba
Copy link
Contributor

aboba commented Dec 23, 2016 •
edited

@vivienlacourba The warnings appear to have originated with respec-w3c-common build 8.0.0 and have not been fixed in build 8.0.1, released two days ago. At least with the ORTC API spec, the problems disappear when utilizing respec-w3c-common.js Build 7.3.2 (the last build prior to removal of "legacy" mode). I checked that version into the github, in case we need to link to it before the respec issue gets fixed.

@aboba aboba added the PR exists label Jan 5, 2017
@alvestrand
Copy link
Contributor

@aboba should make sure there's a link to the PR when adding "PR exists"...

@aboba aboba mentioned this issue Jan 5, 2017
Closed
@aboba aboba removed the PR exists label Jan 5, 2017
@dontcallmedom
Copy link
Member

See #989

@alvestrand
Copy link
Contributor

Mostly fixed by #989 - objects still missing.

@dontcallmedom dontcallmedom mentioned this issue Jan 16, 2017
Closed
dontcallmedom added a commit that referenced this issue Jan 16, 2017
@dontcallmedom
Add more of the missing in-prose definitions
7b430bb 
for #978
dontcallmedom added a commit that referenced this issue Jan 16, 2017
@dontcallmedom
Add missing overloaded anchor for addIceCandidate
3f074b2 
part of #978
@dontcallmedom dontcallmedom mentioned this issue Jan 16, 2017
Merged
@alvestrand
Copy link
Contributor

Hopefully fixed with #995

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Editorial PR exists
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@dontcallmedom @alvestrand @aboba @vivienlacourba