Editorial: Align with Web IDL specification#482

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

markafoltz merged 1 commit intow3c:gh-pagesfromautokagami:presentation-api

Oct 7, 2020

Merged

Editorial: Align with Web IDL specification#482

markafoltz merged 1 commit intow3c:gh-pagesfromautokagami:presentation-api

Oct 7, 2020

Conversation

Copy link

Contributor

autokagami commentedAug 18, 2020•
edited by pr-previewbot
Loading

This is an automated pull request to align the spec with the latest Web IDL specification.

Currently the autofix might introduce some awkward code formatting, so please feel free to modify the formatting.

Please file an issue onhttps://github.com/saschanaz/webidl-updater/issues/new if you think this PR is invalid or should be enhanced.

The following is the validation messages from webidl2.js, which may help understanding this PR:

Validation error at line 8 in presentation-api,6:  void close();  ^ `void` is now replaced by `undefined`. Refer to the [relevant GitHub issue](https://github.com/heycam/webidl/issues/60) for more information.Validation error at line 9 in presentation-api,6:  void terminate();  ^ `void` is now replaced by `undefined`. Refer to the [relevant GitHub issue](https://github.com/heycam/webidl/issues/60) for more information.Validation error at line 17 in presentation-api,6:  void send (DOMString message  ^ `void` is now replaced by `undefined`. Refer to the [relevant GitHub issue](https://github.com/heycam/webidl/issues/60) for more information.Validation error at line 18 in presentation-api,6:  void send (Blob data  ^ `void` is now replaced by `undefined`. Refer to the [relevant GitHub issue](https://github.com/heycam/webidl/issues/60) for more information.Validation error at line 19 in presentation-api,6:  void send (ArrayBuffer data  ^ `void` is now replaced by `undefined`. Refer to the [relevant GitHub issue](https://github.com/heycam/webidl/issues/60) for more information.Validation error at line 20 in presentation-api,6:  void send (ArrayBufferView data  ^ `void` is now replaced by `undefined`. Refer to the [relevant GitHub issue](https://github.com/heycam/webidl/issues/60) for more information.

💥 Error: 500 Internal Server Error 💥

PR Preview failed to build.(Last tried on Aug 18, 2020, 4:34 PM UTC).

PR Preview relies on a number of web services to run. There seems to be an issue with the following one:

🚨Spec Generator - Spec Generator is the web service used to build specs that rely on ReSpec.

🔗Related URL

😭  Sorry, there was an error generating the HTML. Please report this issue!�[36mSpecification: https://rawcdn.githack.com/w3c/presentation-api/57ef841a0ba9e606f5c38ddc3c3352a87de2c723/index.html?isPreview=true&publishDate=2020-08-18�[39m�[36mReSpec version: 25.6.0�[39m�[36mFile a bug: https://github.com/w3c/respec/�[39m�[36mError: Error: Evaluation failed: Timeout: document.respecIsReady didn't resolve in 0ms.�[39m�[36m    at ExecutionContext._evaluateInternal (/u/spec-generator/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:217:19)�[39m�[36m    at runMicrotasks (<anonymous>)�[39m�[36m    at processTicksAndRejections (internal/process/task_queues.js:97:5)�[39m�[36m    at async ExecutionContext.evaluate (/u/spec-generator/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:106:16)�[39m�[36m    at async generateHTML (/u/spec-generator/node_modules/respec/tools/respecDocWriter.js:128:12)�[39m�[36m    at async fetchAndWrite (/u/spec-generator/node_modules/respec/tools/respecDocWriter.js:95:18)�[39m�[36m    at async Object.generate [as respec] (/u/spec-generator/generators/respec.js:14:20)�[39m�[36m    at async generate (/u/spec-generator/server.js:90:29)�[39m�[36m�[39m

If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), pleasefile an issue.