Then +1 to drop it. :-) kind regards
Tobias > Am 20.04.2015 um 13:31 schrieb Martin Grigorov <mgrigo...@apache.org>: > > Hi, > > On Mon, Apr 20, 2015 at 12:42 PM, Tobias Soloschenko < > tobiassolosche...@googlemail.com> wrote: > >> Hi, >> >> Ok this solution sounds good to me: >> >> * Flag for info / error >> * Log into console >> * Ajax Response via Network Tab in Browsers >> >> Thanks for your explanations! :-) >> >> One little question: what about IE6? There is no console object available >> - do you mind to drop the support for that browser in wicket 8? > > I am not sure this is documented officially somewhere but AFAIR we support > IE8+ since Wicket 6.0.0. > > >> >> I don't know the current version of wicket's jquery version. >> >> As of the docs of jquery about IE: >> >> jQuery 1.x - IE 6+ >> jQuery 2.x - IE 9+ > > Thanks to jQuery we didn't have any bug reports against specific version of > a browser. > > >> >> kind regards >> >> Tobias >> >>> Am 20.04.2015 um 09:05 schrieb Martin Grigorov <mgrigo...@apache.org>: >>> >>> Hi Tobias, >>> >>> The debug api of wicket-ajax-jquery.js is: Wicket.Log.(info|error). >>> If the debug window is enabled then both methods log in the debug window >>> and in the JS window.console. >>> If the debug window is disabled then only Wicket.Log.error is enabled and >>> logs in the JS window.console. >>> >>> IMO we can drop the debug window and replace with with a boolean switch >>> that enables logging of INFO messages in the JS console. The INFO message >>> with the XML response should be removed too because this information is >>> available in the Network tab >>> >>> >>> On Sat, Apr 18, 2015 at 12:39 AM, Tobias Soloschenko < >>> tobiassolosche...@googlemail.com> wrote: >>> >>>> Hi, >>>> >>>> please don't drop it because of focus requests and some other debug >>>> information of actions requested on server side - server actions can't >> be >>>> logged at client side, but with the debug window. >>>> >>>> kind regards >>>> >>>> Tobias >>>> >>>>> Am 17.04.2015 um 22:54 schrieb Martin Grigorov <mgrigo...@apache.org>: >>>>> >>>>> Hi, >>>>> >>>>> Do you still use Wicket Ajax Debug window for something when developing >>>>> your applications? >>>>> >>>>> I haven't used it in few years now and it seems I don't miss it. >>>>> I can see all the debug information in the browser's dev tools: >>>>> - ajax response in the Network tab >>>>> - info and error messages in the JS Console tab >>>>> >>>>> Is there something that makes it still useful or we can drop it for >>>> Wicket >>>>> 8? >>>>> >>>>> Martin Grigorov >>>>> Wicket Training and Consulting >>>>> https://twitter.com/mtgrigorov >>
