#4458 closed enhancement (wontfix)
It moves content out of <form> tag.
Reported by: | vrassouli | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 1.7.2 |
Component: | ui.dialog | Version: | 1.7.1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
Whenever you put some portion of a <form> in a dialog, it generates some sort of HTML, and moves the form portion to somewhere else, which is not in the <form> tag! so after submitting the form, you can't get the elements (becouse they are out of form) if you the generated Html for dialog, just in-place, it would solve this problem
Attachments (1)
Change History (7)
comment:1 Changed 14 years ago by
Milestone: | TBD → 1.next |
---|
comment:2 Changed 14 years ago by
I wonder why this important issue has not been yet fixed! of course there's simple workarounds for this, but this still is an open issue!
comment:3 Changed 14 years ago by
i would also like to add a vote to this bug/enhancement. at least an option to disable this behavior. this plays havoc with existing code, and defeats the usual purpose of dialogs... If you use ajax submit its less of a problem... but if you use the most popular jquery validation plugin you will have to resort to ugly work-arounds. sorry to come off as a complainer... if i had time/experience to contribute a fix i would try. non the less, thanks for the great effort, jqui is gold.
comment:4 Changed 13 years ago by
One of the requirements of the dialog is that it appear as the top-most element. The only way to accomplish this consistently in Internet Explorer is to have the dialog be the last element in the body, as it respects DOM order over z-index. There are generally two work-arounds:
- move the dialog element back somewhere else in the dom in the open event callback. This has the potential to allow other elements to appear on top of the dialog (see above)
- move the dialog content element somewhere else in the dom in the close event callback, before the submit.
Neither of these are suitable for building in to the dialog, and are left as suggested work-arounds. As the first comment on this ticket suggests, this needs to be documented better.
comment:5 Changed 13 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:6 Changed 10 years ago by
Milestone: | 1.next → 1.7.2 |
---|
Probably more of a documentation issue.