Re: [beacon] Random comments

On Wed, Feb 12, 2014 at 3:02 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 2/12/14 5:52 PM, Jonas Sicking wrote:
>>
>> I personally think C makes the most sense since it doesn't involve
>> grabbing some omnious global state. Instead the behavior is determined
>> by the more tangible answer to the question "which object did you call
>> a function on".
>
> What object, or what function?
>
> Consider windowC.navigator.sendBeacon.apply(windowD.navigator, args)

I would say D here. Carrying state in functions feels a lot more hacky
than carrying state in objects.

/ Jonas

Received on Wednesday, 12 February 2014 23:34:53 UTC