[ 
https://issues.apache.org/jira/browse/WICKET-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Frank Silbermann updated WICKET-1601:
-------------------------------------

    Attachment: screenshot-1.jpg

Initially, both button groups had the first selection (Ay) chosen.  Here, I 
clicked the third choice of the first group, changing the value of the first 
model variable.  The second radio button group lost its indicator.

> Two RadioGroups on one page interfering with one another
> --------------------------------------------------------
>
>                 Key: WICKET-1601
>                 URL: https://issues.apache.org/jira/browse/WICKET-1601
>             Project: Wicket
>          Issue Type: Bug
>    Affects Versions: 1.3.3
>         Environment: generic
>            Reporter: Frank Silbermann
>         Attachments: myproject.zip, screenshot-1.jpg
>
>
> I created a simple Panel that contains a formatted RadioGroup with 
> wantOnSelectionChangedNotifications() returning true.  (Its constructor 
> accepts an array of options, a PropertyModel to be controlled, and a caption 
> for the label.)  I put two instances of this panel on a single page, each 
> controlling its own model variable.  The page displays the two RadioGroup 
> panels and displays the value of the two model variables.
> When I select a radiobutton from one group, all the radio buttons from the 
> other group become unselected (i.e., the dot indicator disappears) -- as 
> though the radio buttons belonged to the same button group.
> My quickstart project illustrating the behavior (if I can figure out how to 
> attach it) uses Wicket 1.3.3.  Bring up the home page and begin clicking its 
> radio groups to see the behavior.
> I discovered this problem in my Wicket 1.2 application when I tried to 
> upgrade its libraries from Wicket 1.2.2 to Wicket 1.2.6.  (With the new 
> libraries, I also began seeing a great many puzzling new null value errors.)  
> If the bug gets fixed in Wicket 1.3, I'll upgrade my application to it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to