Someone has already reported this issue to mozilla. The bug id is 357103 The status of the bug is UNCONFIRMED and is assigned to
[EMAIL PROTECTED]. Let's vote for this issue to get it fixed.On 27/10/06, Igor Vaynberg <[EMAIL PROTECTED]
> wrote:yes it is the issue.this is nothing we can really fi
yes it is the issue.this is nothing we can really fix - it is the browser's fault. i think only firefox does this but i dont remember for sure. i dont see why when it encounters src="" on an img it sends another request to the url that generated the page. seems silly. they prob dont check for the e
is it the issue described in the entry "best practices and gotchas" in the wiki? This is horrible if it can still happen in 1.2.2. Maybe, this is a feature and not a bug.*PEACE OUT* :-)
On 27/10/06, Flavius <[EMAIL PROTECTED]> wrote:
I found the issue.I'm putting the images in for the home page.On
I found the issue.
I'm putting the images in for the home page.
One tag didn't have an entry for the src, like
http://www.nabble.com/Wicket-1.2.2-home-page-loads-twice-tf2515875.html#a7022847
Sent from the Wicket - User mailing list archive at Nabble.com.
Did you download and see the same effect with the Wicket Quickstart project?
Martijn
On 10/26/06, Flavius <[EMAIL PROTECTED]> wrote:
>
>
> I'm new with wicket and started a vanilla project. I created my application
> class which extends WebApplication and defined a home page called Home.java
> (
does your url of the homepage also change the second time (is there a redirect somehow)or does it just stay /Else place a breakpoint in your constructor and see why or where it comes from the second time for one request.
johanOn 10/26/06, Flavius <[EMAIL PROTECTED]> wrote:
I'm new with wicket and s
Eelco Hillenius wrote:
>
> See my other reply: it was solved by not setting the window.name
> anymore. If you update to trunk (or wait for 1.2.3) your problem
> should be gone.
>
Thanks for your answer. I think I'll wait for 1.2.3 instead of trying to
build wicket on my own. :)
Anyway your hi
> I prepared a small sample, that shows the problem. Just start the
> wickettest.FramePage... The first link, that was clicked in the navigation
> frame appears right, the next one opens a new window. I took a closer look
> to the produced code and found, that the window.name is changed, which
> ca
Yes. This was a problem in Wicket 1.2.2 and is fixed now. In trunk is
also an updated version of wicket-examples/frames that displays how to
use page maps for frames. In case you weren't using a different page
map per frame: it's highly recommended you do so. The page map name
and frame name should
Hi again,
I prepared a small sample, that shows the problem. Just start the
wickettest.FramePage... The first link, that was clicked in the navigation
frame appears right, the next one opens a new window. I took a closer look
to the produced code and found, that the window.name is changed, which
as soon as we fix all the major outstanding bugs we will put out 1.2.3we were hoping for a week since 1.2.2, but it might be a bit longer.-IgorOn 9/1/06,
Adam Smyczek <[EMAIL PROTECTED]> wrote:
Thanks Igor. I will move to 1.x branch.Maybe it is to early to ask since 1.2.2 is just out the door,but
Thanks Igor. I will move to 1.x branch.
Maybe it is to early to ask since 1.2.2 is just out the door,
but do you know how the time frame for 1.2.3 is?
Adam
On Sep 1, 2006, at 2:32 PM, Igor Vaynberg wrote:
> yes you are right, it was a bug. onError() was added long after the
> validating beha
yes you are right, it was a bug. onError() was added long after the validating behavior was created and i didnt think about it. thanks for catching it. its in svn wicket-1.x right now if you want to check that out and will be in
1.2.3-IgorOn 9/1/06, Adam Smyczek <[EMAIL PROTECTED]> wrote:
Yes, you
Yes, you are right, I could add the feedback panel to overridden
onError() method of AjaxSubmitButton,
but my code cannot use it (have some custom submit logic).
I use AjaxFormValidatingBehavior, so for now I subclass it and
override onError().
Additionally I have to implement addToAllFormCompo
You can override onError to react on a failing validation. Updating of
the feedbackpanel should be automatic, as long as you add the
feedbackpanel to the ajax target for re-rendering.
protected void onError(AjaxRequestTarget target) {
target.add(myFeedbackPanel);
}
Eelco
On 9/1/06, Ad
-Ursprüngliche Nachricht-
Wow! Really great looking new fetures!
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easi
Martijn Dashorst wrote:
>
> o Wicket Extensions
> - Backported AJAX header contribution code from 2.0.
Just a very minor detail. AJAX header contribution is part of core, not
extensions (have I put it to wrong changes.xml?).
-Matej
>
> Have fun!
> - The Wicket Team
>
> --
> Downl
1.2.2 is not out yet. It will be out soon, maybe this weekend.
Eelco
On 8/23/06, Nili Adoram <[EMAIL PROTECTED]> wrote:
> Hi all,
> How can I download 1.2.2 ?
> I found no link in wicket download page.
> Thanks
> Nili
>
> -
18 matches
Mail list logo
