Re: Firefox and User Timing API in workers

On Tue, Jun 2, 2015 at 10:24 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:

> That said, the distinction between dedicated vs shared seems
>> redundant, at least as far as time accounting is concerned.
>>
>
> I think you're ignoring the fact that UAs have been shipping the
> "dedicated workers use the timebase of the parent" behavior for a while now.
> Do you have any evidence that the change you propose doesn't break
> existing content?
>

I'm not aware of any such cases, but this is anecdotal on my part. I don't
believe we have any existing counters or telemetry on its use within Chrome
either.. anything in Firefox, or are you aware of any particular
deployments that might be affected?

Is that coherent? :-)
>>
>
> It is, and if we were doing green-field design I could live with it. But
> we're not; we're trying to post-facto specified something that has been
> implemented and shipping for a while, but deliberately specifying it
> incompatibly with implementations.


Yes, that's a fair concern. FWIW, we do know that Safari and IE are yet to
enable performance interface in worker's, so that already significantly
reduces the impact of this change.