Re: [push-api] Rewriting push event handling; allowing data to be optional. (#166)

>            </li>
>          </ol>
>          <p>
>            When a constructor of the <a>PushEvent</a> interface, or of an interface that inherits
>            from the <a>PushEvent</a> interface, is invoked, the usual <a>steps for constructing
> -          events</a> MUST be modified as follows: instead of setting the <code>data</code>
> -          attribute of the event to the value of the <var>eventInitDict</var>'s "<code id=
> -          "widl-PushEventInit-data">data</code>" member, set the <code>data</code> attribute to a
> -          new <a>PushMessageData</a> with <a>bytes</a> set to the result of <a data-lt=
> -          "extract a byte sequence">extracting a byte sequence</a> from that dictionary member, or
> -          an empty byte sequence if the "<code id="widl-PushEventInit-data">data</code>" member is
> -          not provided.
> +          events</a> are modified so that instead of setting the <code>data</code> attribute of the
> +          event to the value of the <var>eventInitDict</var>'s "<code>data</code>" member, set the
> +          <code>data</code> attribute to a new <a>PushMessageData</a> instances with <a>bytes</a>

instances -> instance

In general, this sentence is very hard to parse.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/pull/166/files#r42141682