You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Major Peter (JIRA)" <ji...@apache.org> on 2011/01/13 20:33:45 UTC
[jira] Created: (WICKET-3331) DropDownChoice with
wantOnSelectionChangedNotifications fails without Form
DropDownChoice with wantOnSelectionChangedNotifications fails without Form
--------------------------------------------------------------------------
Key: WICKET-3331
URL: https://issues.apache.org/jira/browse/WICKET-3331
Project: Wicket
Issue Type: Bug
Components: wicket
Reporter: Major Peter
If you have a DDC without a form, then in onSelectionChanged the new selection will be always null. As soon as you put a Form around the DDC, it just starts to work.
Although the HTML 4 DTD does not allow a select tag outside a form, Wicket supported this behaviour, and this feature also worked with 1.5-M3 too.
See the attached project showing that the newSelection is null if the DDC is not inside a form.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (WICKET-3331) DropDownChoice with
wantOnSelectionChangedNotifications fails without Form
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov reassigned WICKET-3331:
---------------------------------------
Assignee: Martin Grigorov
> DropDownChoice with wantOnSelectionChangedNotifications fails without Form
> --------------------------------------------------------------------------
>
> Key: WICKET-3331
> URL: https://issues.apache.org/jira/browse/WICKET-3331
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-RC1
> Reporter: Major Peter
> Assignee: Martin Grigorov
> Attachments: wicket-3331.tar.gz
>
>
> If you have a DDC without a form, then in onSelectionChanged the new selection will be always null. As soon as you put a Form around the DDC, it just starts to work.
> Although the HTML 4 DTD does not allow a select tag outside a form, Wicket supported this behaviour, and this feature also worked with 1.5-M3 too.
> See the attached project showing that the newSelection is null if the DDC is not inside a form.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3331) DropDownChoice with
wantOnSelectionChangedNotifications fails without Form
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov updated WICKET-3331:
------------------------------------
Fix Version/s: (was: 1.5-RC2)
1.5-RC1
> DropDownChoice with wantOnSelectionChangedNotifications fails without Form
> --------------------------------------------------------------------------
>
> Key: WICKET-3331
> URL: https://issues.apache.org/jira/browse/WICKET-3331
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-RC1
> Reporter: Major Peter
> Assignee: Martin Grigorov
> Fix For: 1.5-RC1
>
> Attachments: wicket-3331.tar.gz
>
>
> If you have a DDC without a form, then in onSelectionChanged the new selection will be always null. As soon as you put a Form around the DDC, it just starts to work.
> Although the HTML 4 DTD does not allow a select tag outside a form, Wicket supported this behaviour, and this feature also worked with 1.5-M3 too.
> See the attached project showing that the newSelection is null if the DDC is not inside a form.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3331) DropDownChoice with
wantOnSelectionChangedNotifications fails without Form
Posted by "Major Peter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Major Peter updated WICKET-3331:
--------------------------------
Affects Version/s: 1.5-RC1
> DropDownChoice with wantOnSelectionChangedNotifications fails without Form
> --------------------------------------------------------------------------
>
> Key: WICKET-3331
> URL: https://issues.apache.org/jira/browse/WICKET-3331
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-RC1
> Reporter: Major Peter
> Attachments: wicket-3331.tar.gz
>
>
> If you have a DDC without a form, then in onSelectionChanged the new selection will be always null. As soon as you put a Form around the DDC, it just starts to work.
> Although the HTML 4 DTD does not allow a select tag outside a form, Wicket supported this behaviour, and this feature also worked with 1.5-M3 too.
> See the attached project showing that the newSelection is null if the DDC is not inside a form.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3331) DropDownChoice with
wantOnSelectionChangedNotifications fails without Form
Posted by "Major Peter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Major Peter updated WICKET-3331:
--------------------------------
Attachment: wicket-3331.tar.gz
Quickstart project demonstrating the problem.
> DropDownChoice with wantOnSelectionChangedNotifications fails without Form
> --------------------------------------------------------------------------
>
> Key: WICKET-3331
> URL: https://issues.apache.org/jira/browse/WICKET-3331
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-RC1
> Reporter: Major Peter
> Attachments: wicket-3331.tar.gz
>
>
> If you have a DDC without a form, then in onSelectionChanged the new selection will be always null. As soon as you put a Form around the DDC, it just starts to work.
> Although the HTML 4 DTD does not allow a select tag outside a form, Wicket supported this behaviour, and this feature also worked with 1.5-M3 too.
> See the attached project showing that the newSelection is null if the DDC is not inside a form.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-3331) DropDownChoice with
wantOnSelectionChangedNotifications fails without Form
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-3331.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.5-RC2
Fixed with r1058922
> DropDownChoice with wantOnSelectionChangedNotifications fails without Form
> --------------------------------------------------------------------------
>
> Key: WICKET-3331
> URL: https://issues.apache.org/jira/browse/WICKET-3331
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5-RC1
> Reporter: Major Peter
> Assignee: Martin Grigorov
> Fix For: 1.5-RC2
>
> Attachments: wicket-3331.tar.gz
>
>
> If you have a DDC without a form, then in onSelectionChanged the new selection will be always null. As soon as you put a Form around the DDC, it just starts to work.
> Although the HTML 4 DTD does not allow a select tag outside a form, Wicket supported this behaviour, and this feature also worked with 1.5-M3 too.
> See the attached project showing that the newSelection is null if the DDC is not inside a form.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.