[ https://issues.apache.org/jira/browse/WICKET-6959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500740#comment-17500740 ]
Emond Papegaaij commented on WICKET-6959: ----------------------------------------- Actually, I think Safari has it wrong. This is from the HTML 5 specification https://html.spec.whatwg.org/#the-hidden-attribute {quote}Elements in a section hidden by the hidden attribute are still active, e.g. scripts and form controls in such sections still execute and submit respectively. Only their presentation to the user changes.{quote} > Form#setDefaultButton does not work under Safari > ------------------------------------------------ > > Key: WICKET-6959 > URL: https://issues.apache.org/jira/browse/WICKET-6959 > Project: Wicket > Issue Type: Bug > Affects Versions: 9.7.0, 9.8.0 > Environment: Safari 15.3 > macOS 12.2 > Reporter: felix.rill...@cryptshare.com > Priority: Minor > Attachments: PoC Safari and setDefaultButton.zip > > > setDefaultButton uses a hidden submit component. In most major browsers, this > works well and allows one to submit a form by pressing 'Enter' while in a > e.g. TextField. > Safari seems to ignore the hidden submit component, which makes it impossible > to submit the form by using 'Enter' if the submit button is outside the form > (attached is a Proof of Concept). > If instead of using the HTML 'hidden' attribute, the hidden submit component > is made invisible by other means (e.g. moving it outside the viewport), it > works. > > As the JavaDoc of setDefaultButton already state "note that this is a best > effort only", this probably not a priority. -- This message was sent by Atlassian Jira (v8.20.1#820001)