My best guess is that IE is trying to GET the contents pointed to by the
link, and at the same time process your onClick event, and the two are
conflicting. That is just a guess, but I have indeed seem similar
behavior when using a link. One thing you can do is to not make it a link
at all, inste
Though this problem was resolved long time back, I was just wondering what
the actual problem was.
The problem was resolved just by replacing
Next
with
Using the anchor tag, the HTTPWatch showed that the HTTP operation was
aborted by IE, where as by using the button it went on the next page
Aborted can happen when a proxy is involved, which has been suggested
before as the source of your troubles. I think it would be in your best
interest to purchase HTTPWatch to see the full details, or else find a
free alternative... some options:
http://www.siliconwold.com/interceptor/interce
Hi Dave,
I have used the basic edition of HttpWatch and found these results after
clicking "next"
Started Time size method Result Type
00:01:58.5120.004*POSTAborted*
URL
http://localhost:8080/WITRApplication/GetOtherSet.do?nextposition=10&rand=93395784
00:02:1
zahid mohammed wrote:
> If something was fundamentally wrong then why would it work in "FIREFOX".
>
Perhaps because Firefox is less fundamentally broken than IE?
> And moreover these two printlns are giving the same result in Firefox but
> not in IE i.e after clicking next these are printing the
If something was fundamentally wrong then why would it work in "FIREFOX".
And moreover these two printlns are giving the same result in Firefox but
not in IE i.e after clicking next these are printing the next page's first
element. I am in the process of using HTTPWatch. I'll let u guys know the
re
zahid mohammed wrote:
> Yes. After clicking next "System.out.println" is printing the right name on
> the console whereas "out.println" is printing the wrong name (first page
> element) on the jsp.
>
Well, it certainly wouldn't be the first page element. It's after a
logic:iterate and table etc.
Yes. After clicking next "System.out.println" is printing the right name on
the console whereas "out.println" is printing the wrong name (first page
element) on the jsp.
Thanks
On 2/17/06, Dave Newton <[EMAIL PROTECTED]> wrote:
>
> zahid mohammed wrote:
> >> System.out.println("The First cand
zahid mohammed wrote:
> One thing which surprises me is the difference in behavior of "
> System.out.println" and the "out.println" statements. The former statement
> is printing the write set of elements on the console whereas the "
> out.println" is printing the wrong set of elements on the jsp.
I am not using any network "speedup" mechanisms.
If the application was'nt working in Firefox I would have thought there
might be some problem in the code, but its working great in firefox which
means there is no problem in the code.
One thing which surprises me is the difference in behavior of "
10 matches
Mail list logo