On Thursday, May 8, 2014 11:10:22 AM UTC+2, Markus Staab wrote: > > One possible problem is the time synchronization between the client and >> the server. If it's off the event's coming from the server want match the >> Net pane's (client) timeline properly. >> > thats right. I thougt about using timestamps relative to the > server-request start time and let the browser calculate the exact point in > time using performance.timing API. > The browsers time is not available at the server, right? > Right
> > >> I would send the data rather through HTTP headers. >> See this issue report that's related: >> https://code.google.com/p/fbug/issues/detail?id=1714 >> >> But I am not sure whether you want to actually build Firebug extension >> (or direct Firebug patch) that allows all that automatically. >> > > I would like to built such thing without a Firebug extension. Also thought > about using http headers for it, but this would only solve my problem using > server-side things. > I think there are even more use-cases which could be solved if there were > a JS api doing stuff like that. > I see > > > >> It could be enough to use internal API, in case you want to build a >> Firebug feature. >> >> Otherwise we could teach the console.timeStamp to use new Date >> argument... (and a label) >> > > exactly what I would like to have ;-). > I think that the best next step would be creating an issue report + a test case I can suggest a patch related to the console.timeStamp API Honza > > Thanks, > Markus > -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/1d0cbde2-be24-4e29-9ba9-e0bca5870ac2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
