The following is the validation messages from webidl2.js, which may help understanding this PR:
Validation error at line 6 in portals,0:
[NewObject] Promise<void> activate(optional
^ `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 6 in portals,0, inside `interface HTMLPortalElement -> operation activate -> argument options`:
> activate(optional PortalActivateOptions options);
^ Optional dictionary arguments must have a default value of `{}`.
Validation error at line 7 in portals,0:
void postMessage(any 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 3 in portals,2:
void postMessage(any 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 3 in portals,2, inside `interface PortalHost -> operation postMessage -> argument options`:
any message, optional PostMessageOptions options);
^ Optional dictionary arguments must have a default value of `{}`.
Validation error at line 1 in portals,4, inside `typedef MessageEventSource`:
or HTMLPortalElement or PortalHost) MessageEventSource;
^ The name "MessageEventSource" of type "typedef" was already seen
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 on https://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:
Preview | Diff