On Tue, Jun 2, 2015 at 1:20 PM, Ilya Grigorik wrote:
> On Tue, Jun 2, 2015 at 11:14 AM, Boris Zbarsky wrote:
>
>> On 6/2/15 2:07 PM, Ilya Grigorik wrote:
>>
>>> anything in Firefox, or are you aware of any
>>> particular deployments that might be affected?
>>>
>>
>> No on both counts. I just kn
On Tue, Jun 2, 2015 at 11:14 AM, Boris Zbarsky wrote:
> On 6/2/15 2:07 PM, Ilya Grigorik wrote:
>
>> anything in Firefox, or are you aware of any
>> particular deployments that might be affected?
>>
>
> No on both counts. I just know we've been shipping this for a while and
> so has Chrome and r
On 6/2/15 12:37 PM, Ilya Grigorik wrote:
On that note, I'd love to get someone from Mozilla on our calls, and if
needed we can adjust the time.. Boris, Jonas: is there an alternative
time that would work better for either of you?
For me, the problem is that my schedule is highly variable. So i
On 6/2/15 2:07 PM, Ilya Grigorik wrote:
anything in Firefox, or are you aware of any
particular deployments that might be affected?
No on both counts. I just know we've been shipping this for a while and
so has Chrome and right now we have compatible behavior and this
behavior is not what yo
On Tue, Jun 2, 2015 at 10:24 AM, Boris Zbarsky 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
On 6/2/15 1:18 PM, Ilya Grigorik wrote:
As Jonas outlined, there are valid use cases for doing time accounting
against both the parents timebase and own start time.
While true, the vast majority of uses of dedicated workers I've seen
align more closely with the "parent timebase" use cases...
On Thu, May 28, 2015 at 3:33 PM, Jonas Sicking wrote:
> On Wed, May 27, 2015 at 5:56 PM, Boris Zbarsky wrote:
> > On 5/27/15 6:01 PM, Ilya Grigorik wrote:
> >>
> >> That's what I meant to say.. Single attribute that works across all
> >> worker cases :)
> >
> > And I'm saying I'd prefer a single
On Fri, May 29, 2015 at 9:45 AM, Boris Zbarsky wrote:
> On 5/29/15 11:09 AM, Ilya Grigorik wrote:
>
>> In the meantime, would either of you guys be able to join next week's
>> conf call -- Jun 3rd, 12PM PST?
>>
>
> I won't be able to, for the same reason as I couldn't join this week's: I
> have a
On 5/29/15 11:09 AM, Ilya Grigorik wrote:
In the meantime, would either of you guys be able to join next week's
conf call -- Jun 3rd, 12PM PST?
I won't be able to, for the same reason as I couldn't join this week's:
I have a standing commitment on Wednesdays at that time through the end
of th
Boris, Jonas, thanks.. owe you a reply on both of those once this I/O thing
has blown over :)
In the meantime, would either of you guys be able to join next week's conf
call -- Jun 3rd, 12PM PST? In addition to what we're discussing in this
thread, I'd love to hear your thoughts and feedback on FT
On Wed, May 27, 2015 at 5:56 PM, Boris Zbarsky wrote:
> On 5/27/15 6:01 PM, Ilya Grigorik wrote:
>>
>> That's what I meant to say.. Single attribute that works across all
>> worker cases :)
>
> And I'm saying I'd prefer a single attribute that works across all globals
> period and represents the z
On 5/27/15 6:01 PM, Ilya Grigorik wrote:
That's what I meant to say.. Single attribute that works across all
worker cases :)
And I'm saying I'd prefer a single attribute that works across all
globals period and represents the zero time of the monotonic clock in
that global, so people don't ha
On Wed, May 27, 2015 at 11:53 AM, Boris Zbarsky wrote:
>
> Right, as written its SW specific.. I think we can make it work in both
>> cases though.
>>
>
> Can we just have a property that works in all cases (workers, windows,
> etc) so people can just write their code without worrying about where
As soon as the spec is updated, I'll do the changes in gecko.
To me it's important to have a starting time for Workers and
navigationStart was a reasonable value, but I'm happy to use workerStart.
We just landed the code in m-i and it's already in the nightly builds. But
if the spec is quickly upda
On 5/27/15 2:41 PM, Ilya Grigorik wrote:
Ah, good catch, missed that in the earlier update. Opened a bug to track
this:
https://github.com/w3c/resource-timing/issues/23
Thanks!
Right, as written its SW specific.. I think we can make it work in both
cases though.
Can we just have a property
On Mon, May 25, 2015 at 4:13 AM, Andrea Marchesini
wrote:
> 2. PerformanceTiming is not exposed to workers. The only attribute that
>>> can be used as marker name is 'navigationStart'.
>>>
>>
>> Not sure I follow this. Why are the marker names restricted? Is this
>> related to: https://github.com
On Fri, May 22, 2015 at 10:24 PM, Boris Zbarsky wrote:
>
> https://w3c.github.io/resource-timing/#terminology clearly says:
>
> Throughout this work, all time values are measured in milliseconds
> since the start of navigation of the document. For example, the
> start of navigation of the do
> 2. PerformanceTiming is not exposed to workers. The only attribute that
>> can be used as marker name is 'navigationStart'.
>>
>
> Not sure I follow this. Why are the marker names restricted? Is this
> related to: https://github.com/w3c/user-timing/issues/1 -- ?
>
It's about this "The *startMark
On 5/22/15 4:54 PM, Ilya Grigorik wrote:
We've recently updated Resource Timing [1] to be exposed to Workers
https://w3c.github.io/resource-timing/#terminology clearly says:
Throughout this work, all time values are measured in milliseconds
since the start of navigation of the document. Fo
+kenji, ksakamoto
Hi Andrea. Thanks for the heads up!
FWIW, I believe the spec omission is an oversight on this end. We've
recently updated Resource Timing [1] to be exposed to Workers and we just
need to do the same for User Timing. Also, similar bug on Chrome side:
https://code.google.com/p/chr
Hi all,
I have recently worked on the porting of user timing API in workers in
Firefox. The reason why this is needed is because it will allow the user to
do some useful benchmark when content is loaded and managed from/by
ServiceWorkers. But it's also useful for performance analysis of worker
cod
21 matches
Mail list logo
