You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Andrew Lombardi (JIRA)" <ji...@apache.org> on 2007/05/30 09:12:15 UTC
[jira] Created: (WICKET-601) RadioGroup and CheckGroup cause XHTML
validation errors because of name attribute
RadioGroup and CheckGroup cause XHTML validation errors because of name attribute
---------------------------------------------------------------------------------
Key: WICKET-601
URL: https://issues.apache.org/jira/browse/WICKET-601
Project: Wicket
Issue Type: Bug
Components: wicket
Reporter: Andrew Lombardi
When using RadioGroup's or CheckGroup's, they usually are enclosed in a <span> or similar non-block element. Ordinarily you can just render the body, but if you're using ajax on the radio/check inside, you can't do that. This causes an XHTML validation error since span doesn't have a name attribute, neither does div, etc. What I've done in my code is the following:
protected void onComponentTag(final ComponentTag tag) {
super.onComponentTag(tag);
tag.remove("name");
}
This makes the page validate now, thoughts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-601) RadioGroup and CheckGroup cause XHTML
validation errors because of name attribute
Posted by "Alastair Maw (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alastair Maw updated WICKET-601:
--------------------------------
Fix Version/s: 1.3.0-rc1
> RadioGroup and CheckGroup cause XHTML validation errors because of name attribute
> ---------------------------------------------------------------------------------
>
> Key: WICKET-601
> URL: https://issues.apache.org/jira/browse/WICKET-601
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Reporter: Andrew Lombardi
> Fix For: 1.3.0-rc1
>
>
> When using RadioGroup's or CheckGroup's, they usually are enclosed in a <span> or similar non-block element. Ordinarily you can just render the body, but if you're using ajax on the radio/check inside, you can't do that. This causes an XHTML validation error since span doesn't have a name attribute, neither does div, etc. What I've done in my code is the following:
> protected void onComponentTag(final ComponentTag tag) {
> super.onComponentTag(tag);
> tag.remove("name");
> }
> This makes the page validate now, thoughts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-601) RadioGroup and CheckGroup cause
XHTML validation errors because of name attribute
Posted by "Tim Schafer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500265 ]
Tim Schafer commented on WICKET-601:
------------------------------------
Same problem with CheckBoxMultipleChoice
> RadioGroup and CheckGroup cause XHTML validation errors because of name attribute
> ---------------------------------------------------------------------------------
>
> Key: WICKET-601
> URL: https://issues.apache.org/jira/browse/WICKET-601
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Reporter: Andrew Lombardi
>
> When using RadioGroup's or CheckGroup's, they usually are enclosed in a <span> or similar non-block element. Ordinarily you can just render the body, but if you're using ajax on the radio/check inside, you can't do that. This causes an XHTML validation error since span doesn't have a name attribute, neither does div, etc. What I've done in my code is the following:
> protected void onComponentTag(final ComponentTag tag) {
> super.onComponentTag(tag);
> tag.remove("name");
> }
> This makes the page validate now, thoughts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (WICKET-601) RadioGroup and CheckGroup cause XHTML
validation errors because of name attribute
Posted by "Alastair Maw (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alastair Maw reassigned WICKET-601:
-----------------------------------
Assignee: Alastair Maw
> RadioGroup and CheckGroup cause XHTML validation errors because of name attribute
> ---------------------------------------------------------------------------------
>
> Key: WICKET-601
> URL: https://issues.apache.org/jira/browse/WICKET-601
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Reporter: Andrew Lombardi
> Assignee: Alastair Maw
> Fix For: 1.3.0-rc1
>
>
> When using RadioGroup's or CheckGroup's, they usually are enclosed in a <span> or similar non-block element. Ordinarily you can just render the body, but if you're using ajax on the radio/check inside, you can't do that. This causes an XHTML validation error since span doesn't have a name attribute, neither does div, etc. What I've done in my code is the following:
> protected void onComponentTag(final ComponentTag tag) {
> super.onComponentTag(tag);
> tag.remove("name");
> }
> This makes the page validate now, thoughts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-601) RadioGroup and CheckGroup cause XHTML
validation errors because of name attribute
Posted by "Alastair Maw (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alastair Maw resolved WICKET-601.
---------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.3.0-rc1)
1.3.0-beta3
Fixed in trunk.
> RadioGroup and CheckGroup cause XHTML validation errors because of name attribute
> ---------------------------------------------------------------------------------
>
> Key: WICKET-601
> URL: https://issues.apache.org/jira/browse/WICKET-601
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Reporter: Andrew Lombardi
> Assignee: Alastair Maw
> Fix For: 1.3.0-beta3
>
>
> When using RadioGroup's or CheckGroup's, they usually are enclosed in a <span> or similar non-block element. Ordinarily you can just render the body, but if you're using ajax on the radio/check inside, you can't do that. This causes an XHTML validation error since span doesn't have a name attribute, neither does div, etc. What I've done in my code is the following:
> protected void onComponentTag(final ComponentTag tag) {
> super.onComponentTag(tag);
> tag.remove("name");
> }
> This makes the page validate now, thoughts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-601) RadioGroup and CheckGroup cause
XHTML validation errors because of name attribute
Posted by "Tim Schafer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500264 ]
Tim Schafer commented on WICKET-601:
------------------------------------
It also causes an HTML validation error, as those attributes aren't allow in
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
either
> RadioGroup and CheckGroup cause XHTML validation errors because of name attribute
> ---------------------------------------------------------------------------------
>
> Key: WICKET-601
> URL: https://issues.apache.org/jira/browse/WICKET-601
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Reporter: Andrew Lombardi
>
> When using RadioGroup's or CheckGroup's, they usually are enclosed in a <span> or similar non-block element. Ordinarily you can just render the body, but if you're using ajax on the radio/check inside, you can't do that. This causes an XHTML validation error since span doesn't have a name attribute, neither does div, etc. What I've done in my code is the following:
> protected void onComponentTag(final ComponentTag tag) {
> super.onComponentTag(tag);
> tag.remove("name");
> }
> This makes the page validate now, thoughts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.