Yes, yours are exactly the *SAME *with mine. older version <15.0 works perfect. But when trying 16.0, 17.0, *Both *of them show (most) DNS and connect time as block time (especially the first few objects).
I guess this should be a bug somewhere... how could we report this bug to the correct place? Hope the problem can be solved as soon as possible. cui 2012/11/22 Adrian Yee <[email protected]> > Is there a bug ticket for this? I tried with Firefox 17.0 and Firebug > 1.10.6 on Linux with a fresh profile and it was sometimes okay (proper > timings), but mostly DNS and connection time got lumped into blocking time. > > Trying older versions of Firefox, it looks like it works fine in 14.0.1, > but has been broken since 15.0. > > Adrian > > > On 11/14/12 01:17, Sebastian Zartner wrote: > >> 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 >> firebug+unsubscribe@**googlegroups.com<firebug%[email protected]> >> For more options, visit this group at >> https://groups.google.com/**forum/#!forum/firebug<https://groups.google.com/forum/#!forum/firebug> >> > > -- > 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 > firebug+unsubscribe@**googlegroups.com<firebug%[email protected]> > For more options, visit this group at > https://groups.google.com/**forum/#!forum/firebug<https://groups.google.com/forum/#!forum/firebug> > -- 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
