The context for fetching the beacon should be "beacon" about beacon HOT 5 CLOSED

I don't recall why/how we arrived at "ping" in current spec.. Guessing, it was used because we didn't have "beacon" in the Fetch spec at the time. That said, aside from providing more accurate context, does this (change to "beacon") have any effect on request processing, etc?

from beacon.

I don't recall why/how we arrived at "ping" in current spec.. Guessing, it was used because we didn't have "beacon" in the Fetch spec at the time. That said, aside from providing more accurate context, does this (change to "beacon") have any effect on request processing, etc?

No, it shouldn't. But note that this is now observable to script through the context attribute of the Request object attached to FetchEvents dispatched to service workers. I don't think this was observable before service workers.

from beacon.

We changed to have both "beacon" and "ping" because people preferred for each somewhat unique context to have its own identifier.

from beacon.

@ehsan @annevk makes sense, thanks. Sounds like a straightforward fix...

from beacon.

Merged. Thank you Ehsan.

from beacon.