[
https://issues.apache.org/jira/browse/ISIS-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303411#comment-14303411
]
Martin Grigorov commented on ISIS-1014:
---------------------------------------
I think I've found the reason for "3. The user has to click twice on the OK
button in order to invoke the modal window.".
The problem occurs only when after editing a field it fires update for the
other fields, i.e. the field has JS event binding for "change" event that
updates the possible values for the other fields (usually Select2 dropdowns).
During the 'change' Ajax call the veil prevents any clicks anywhere on the
page, including the "OK" button. The veil is shown with "fade(1000)", i.e. it
appears invisible (opacity: 0) and in a second it is visible (opacity 0.5).
If the Ajax call return earlier (e.g. it finishes in 100ms) then the veil is
not noticeable by the user but the mouse click is ignored no matter what.
> Modal window improvements
> -------------------------
>
> Key: ISIS-1014
> URL: https://issues.apache.org/jira/browse/ISIS-1014
> Project: Isis
> Issue Type: Improvement
> Components: Viewer: Wicket
> Affects Versions: viewer-wicket-1.8.0
> Reporter: Jeroen van der Wal
> Assignee: Martin Grigorov
> Priority: Minor
> Fix For: viewer-wicket-1.8.0
>
>
> 1. Currently the modal window is located at the top of the screen. We would
> prefer putting it in the center of the screen. The animation time can be
> eliminated or reduced and could come out of the center.
> 2. We have a request that the user can move the modal window: she wants to be
> able to see underlying figures sometimes.
> 3. The user has to click twice on the OK button in order to invoke the modal
> window.
> 4. Make pressing the enter key invoke the OK action.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
