is there a jira issue for this patch?

On Sat, May 10, 2008 at 12:34 AM, PITI <[EMAIL PROTECTED]> wrote:

>
> I had a similar problem. In wicket-ajax.js, I made the following changes,
> and
> now it works fine :
>
> if (Wicket.Focus && Wicket.Focus.lastFocusId) {
>     t.setRequestHeader("Wicket-FocusedElementId", Wicket.Focus.lastFocusId
> || "");
> }
> else {
>    // t.setRequestHeader("Wicket-FocusedElementId", "");
> }
>
> Hope this helps.
>
>
>
> bglynn wrote:
> >
> > I'm also having either the same issue or one very similar.
> >
> > The problem I'm seeing seems to be isolated to IE. The specific build
> > version of IE 7.0.5730.11. The issue only seems to have come up on one
> of
> > 5 machines and assuming the specific IE build maybe an issue.
> >
> > Here's a description:
> > We are using a AjaxLazyLoadPanel to load a long running panel. As soon
> as
> > the panel is is loaded a javascript error of "invalid argument" is
> thrown
> > and the ajax request is halted. Doing some debugging revealed that the
> > exception was being thrown from
> > "t.setRequestHeader("Wicket-FocusedElementId",
> > Wicket.Focus.lastFocusId || "");". The Wicket.Focus.lastFocusId variable
> > is to "", which doesn't seem like it would cause a problem given the OR
> > operator.
> >
> > I'd really apperciate some assitance.
> >
> > Thanks,
> > Brian Glynn
> >
> >
> >
> > atul singh-5 wrote:
> >>
> >> Hi,
> >> I wanted to know about preCallHandlers in wicket-ajax.js .What are they
> >> and
> >> How are they related in java code.
> >> Actually I am facing a problem in internet explorer. The ajax get call
> >> give
> >> error after "Invoking pre-call handler(s).."
> >> It gives an error in the highlighted portion and then all ajax stops
> >> working, because this get call did not return.
> >> The error says--"invalid argument"
> >> I will really appreciate any help. Also if anyone know a javascript
> >> debugger/debugging technique for internet explorer, please let me know,
> >> so i
> >> will be able to do something about this :(..
> >>
> >> Thanks
> >>
> >>
> >>     doGet: function() {
> >>         if (this.precondition()) {
> >>
> >>             this.transport = Wicket.Ajax.getTransport();
> >>
> >>             var url = this.createUrl();
> >>             this.log("GET", url);
> >>
> >>             Wicket.Ajax.invokePreCallHandlers();
> >>
> >>           *  var t = this.transport;**
> >>             if (t != null) {
> >>                 if (Wicket.Browser.isGecko()) {
> >>                     var href = document.location.href;
> >>                     var lastIndexOf = href.lastIndexOf('/');
> >>                     if (lastIndexOf > 0)
> >>                     {
> >>                         url = href.substring(0,lastIndexOf+1) + url;
> >>                     }
> >>                 }
> >>                 t.open("GET", url, this.async);
> >>                 t.onreadystatechange =
> >> this.stateChangeCallback.bind(this);
> >>                 // set a special flag to allow server distinguish
> between
> >> ajax and non-ajax requests
> >>                 t.setRequestHeader("Wicket-Ajax", "true");
> >>                 t.setRequestHeader("Wicket-FocusedElementId",
> >> Wicket.Focus.lastFocusId || "");
> >>                 t.setRequestHeader("Accept", "text/xml");
> >>                 t.send(null);
> >>                 return true;*
> >>             } else {
> >>                 this.failure();
> >>                    return false;
> >>             }
> >>         } else {
> >>             Wicket.Log.info("Ajax GET stopped because of precondition
> >> check,
> >> url:" + this.url);
> >>             this.done();
> >>             return true;
> >>         }
> >>     }
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/javascript-error-in-internet-explorer-tp16732896p17157574.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to