[
https://issues.apache.org/jira/browse/WICKET-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485066
]
Eelco Hillenius commented on WICKET-18:
---------------------------------------
A non-modal modal window... :) Seriously, should the name be changed if this
patch would be accepted?
Also, I'm wondering - though without taking a look at the patch - if this is
not going to be too much of a kitchen sink component. I mean, there's tons of
options out there for internal popups in Javascript libs such as YUI or Dojo
and such... at some point we should choose between keeping a component simple
and focussed or being a thing that does the dishes and ironing on top of being
a modal window.
I don't feel that strongly about it, as I'm not the unlucky bastard maintaining
it at this point, but I can totally imagine this feature opening the way for
newer, crazier feature requests.
Just my 2c.
> Make modal window non-modal
> ---------------------------
>
> Key: WICKET-18
> URL: https://issues.apache.org/jira/browse/WICKET-18
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-extensions
> Affects Versions: 1.2.3
> Reporter: Vincent van den Noort
> Assigned To: Martijn Dashorst
> Attachments: patch.txt
>
>
> We have the requirement for a pop-up div that is not modal. Supplied patch
> creates a non-modal window, allowing users to drag the window and work with
> the underlying page.
> Missing feature: correctly detect and track multiple window instances
> works for both panel and page variants
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
