[
https://issues.apache.org/jira/browse/WICKET-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jor updated WICKET-2214:
------------------------
Component/s: (was: wicket)
Description:
There is an extra form tag in modal window html code (modal.js ->
Wicket.Window.getMarkup function), it causes problems when ModalWindow is used
with panel that contain forms.
I haven't found any use for that form tag as it cannot be referenced from java
code (it has no wicket id) and it only causes problems by creating nested form
tags (outter form from modal html with no wicket id and inner form from panel
with wicket id) that some browsers cant handle and its againts W3C html
specification.
I had to replace it with div tag to get my panel working.
was:
There is an extra form tag in modal window html code (modal.js ->
Wicket.Window.getMarkup function), it causes problems when modal window is used
with panels that contain forms.
I haven't found any use for that form tag as it cannot be referenced from java
code (it has no wicket id) and it only causes problems by creating nested form
tags (outter form from modal html with no wicket id and inner form from panel
with wicket id) that some browsers cant handle and its againts W3C html
specification.
I had to replace it with div tag to get my panel working.
Affects Version/s: 1.4-M1
1.4-M2
1.4-M3
1.4-RC1
1.4-RC2
Summary: Form tag in ModalWindow html code causes nested html
forms when ModalWindow is used with panel that contain forms (was: Form tag in
modal window html code (modal.js -> Wicket.Window.getMarkup))
> Form tag in ModalWindow html code causes nested html forms when ModalWindow
> is used with panel that contain forms
> -----------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-2214
> URL: https://issues.apache.org/jira/browse/WICKET-2214
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 1.3.5, 1.4-M1, 1.4-M2, 1.4-M3, 1.4-RC1, 1.4-RC2
> Reporter: Jor
> Attachments: modal.js.patch
>
>
> There is an extra form tag in modal window html code (modal.js ->
> Wicket.Window.getMarkup function), it causes problems when ModalWindow is
> used with panel that contain forms.
> I haven't found any use for that form tag as it cannot be referenced from
> java code (it has no wicket id) and it only causes problems by creating
> nested form tags (outter form from modal html with no wicket id and inner
> form from panel with wicket id) that some browsers cant handle and its
> againts W3C html specification.
> I had to replace it with div tag to get my panel working.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
