Imho the overall user experience in Chrome is better, including the developer tools. Even if it might miss a feature of two :-)
Eelco On Mon, May 23, 2011 at 10:52 AM, Martin Grigorov <mgrigo...@apache.org> wrote: > Well, I don't share your opinion here :-) > > Chrome Dev tools have no "persist console content" - once you reload the > page all the logs are gone. There is a RFE for that and I voted for it. > Also I miss the 'Net' tab. > Also Firefox's WebDeveloper tools are much better than current state in > Chrome and its extensions. > > On Mon, May 23, 2011 at 8:45 PM, Brown, Berlin [GCG-PFS] < > berlin.br...@primerica.com> wrote: > >> FYI... >> >> I usually ask questions but I thought I post a comment about google >> chrome. The chrome browser has default web debugging that is similar to >> firebug. >> >> With Firebug, it is more difficult to detect the wicket ajax rendered >> content but comes up automatically in chrome. Also speed wise, chrome >> renders much faster than IE or Firefox. I tested Ajax oriented complex >> content and chrome just works quickly. >> > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com <http://jweekend.com/> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
