I'm guessing it's probably an artifact of how the underlying tab loading code works that the extensions system hooks into. Rafael might be able to comment here.
If you call chrome.tabs.get() during this "waiting" period, does the url still come back as null? On Mon, Dec 7, 2009 at 2:45 PM, std <std.de...@gmail.com> wrote: > > The tab will initially be created with a null url > Antony, do you have any clue why it is implemented in this way? > It is a bit annoying so when trying to open a link that currently > could not be served [like DNS fault or dropped Wi-Fi] - got no current > URL displayed in omni-bar, nor a way to retry an attempt with Esc -> > F5 :( > > -- > > You received this message because you are subscribed to the Google Groups > "Chromium-extensions" group. > To post to this group, send email to chromium-extensi...@googlegroups.com. > To unsubscribe from this group, send email to > chromium-extensions+unsubscr...@googlegroups.com<chromium-extensions%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/chromium-extensions?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensi...@googlegroups.com. To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
