I can confirm this using FF 16.0.2 (fresh profile) + FB 1.10.6 on Win7. There I do see some milliseconds spent on DNS lookup and connection when accessing https://getfirebug.com after deleting the browser history and deactivating the browser cache. But when the browser cache is enabled, there's no time spent on DNS lookup and connecting. Testing the same using FF 13.0.1 there's always some time spent on DNS lookup and connection. So to me this looks obviously like a change in the Firefox logic. Honza, do you know of any change regarding this?
Sebastian On Thursday, November 8, 2012 9:58:47 PM UTC+1, webs wrote: > > Hi all, > > recently, I updated my firefox browser into newer version of 16.0. > However, I found a strange behavior after the updating: > > By using firebug, when browsing a new page, I found firebug does *not > *provide the DNS lookup time and connecting time *correctly*. > > Two examples are shown in the attachments for browsing google and > mozilla pages. These pages are browsed with empty browsing history, so, at > the beginning, there MUST be DNS lookup and connecting. But, instead, as > seen from these figures, for the first few objects, Firebug report them > with "Blocking" at first, and then, directly comes into "waiting". > > Could some of you have some better explanations for that? is it a bug > in recent firefox? or some event not correctly triggered in firebug? should > we report the bug somewhere else? > > thanks very much > > ps, I am using firebug version 1.10.6, and I tested with many PCs and > network connection environment, it always like that when using version 16 > of firefox. > > best regards > cui > > > > > -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at https://groups.google.com/forum/#!forum/firebug
