[
https://issues.apache.org/jira/browse/ISIS-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13785052#comment-13785052
]
ASF subversion and git services commented on ISIS-552:
------------------------------------------------------
Commit 1dd9e813c86647fdb62ec459c7898f8cef37cf7b in branch refs/heads/master
from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=1dd9e81 ]
ISIS-552: upgrade to Wicket 6.11 ...
taking advantage of the reverted behavior w.r.t. HTML5 attributes
> Upgrade to Wicket 6.11.0 and disable HTML5 functionality that caused
> interference between required text fields and the Wicket viewer's veil.
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISIS-552
> URL: https://issues.apache.org/jira/browse/ISIS-552
> Project: Isis
> Issue Type: Bug
> Components: Viewer: Wicket
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: viewer-wicket-1.3.0
>
>
> In Wicket 6.10.0 (per https://issues.apache.org/jira/browse/WICKET-5289),
> sets the HTML5 "required" attribute. This causes HTML5 browsers such as
> Chrome to display a client-side pop-up.
> When the OK button is clicked, the Wicket viewer always displays the veil
> (see jquery.isis.viewer.wicket.js), and relies upon a page refresh to clear
> the veil.
> However, because the page is never submitted, the veil does not disappear.
> The only workaround is to resubmit the page, thus losing any text that might
> have been entered.
> In Wicket 6.11.0, a new HTML5Attributes feature (WICKET-5331) makes this
> behaviour pluggable.
> This ticket was previously to disable the setRequired flag for Wicket 6.10.0.
> With the advent of Wicket 6.11.0, it is instead to upgrade to Wicket 6.11.0
> and to use this new feature.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
