[
https://issues.apache.org/jira/browse/WICKET-5324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13747474#comment-13747474
]
Jonas commented on WICKET-5324:
-------------------------------
Maybe I'm missing something, but according to http://validator.w3.org the
following document isn't valid because of the html5 attributes 'required' and
'formnovalidate':
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml";>
<head>
<title>Conforming XHTML 1.0 Transitional Template</title>
</head>
<body>
<form action="bla">
<input type="text" required="required" />
<input type="submit" formnovalidate="formnovalidate" />
</form>
</body>
</html>
So it's no longer possible to generate a valid XHTML 1.0 Transitional page
using wicket, as wicket forces those html5 attributes into the input tags.
Right?
IMHO wicket shouldn't force me to use html 5 to get valid html output. I would
have to subclasse each and every text component to get rid if those html5
attributes, that's why I strongly suggest you introduce some kind of setting to
control this properly.
Besides, even if the page is html 5, people might not want to use the browser
based validation, as it is somewhat poor compared to what you can do in
wicket's form validation. IMHO it is a bad default to enforce 'required'
attributes, as it is quite hard to override it.
> HTML5 "required" attributes on required fields break
> 'setDefaultFormProcessing(false)'
> --------------------------------------------------------------------------------------
>
> Key: WICKET-5324
> URL: https://issues.apache.org/jira/browse/WICKET-5324
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.10.0
> Environment: Wicket 6.10.0, Firefox 23.0.1
> Reporter: Jonas
> Priority: Blocker
>
> After updating to Wicket 6.10.0, all Buttons that use
> setDefaultFormProcessing(false) no longer work properly if there are any
> TextFields with required=true on the page, as such fields are now decorated
> with HTML5 "required" attributes that keep the browser from submitting the
> form.
> WICKET-5289 introduced those HTML5 "required" attributes, I guess this change
> should be reverted.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
