#10351 closed defect (invalid)
1.4b2 form overuns it's parent's boundaries
| Reported by: | spidey2099 | Owned by: | |
|---|---|---|---|
| Priority: | high | Milestone: | tbd |
| Component: | Dijit | Version: | 1.4.0b |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description
I am using 1.4b2. When form widgets are added to a form asynchronously, the form will automatically grow to accommodate the added widgets. However - the growing form can exceed the boundaries of it's parent - in this case a content pane. When this happens the scrollbar (which used to appear in 1.3.2) does not appear and the form simply overruns it's parents boundaries.
I have tried setting the property overflow to auto (overflow:auto), but it does not work. Note that the containing node - a content pane - has it's height set to auto. Does this contribute to the problem?
Attachments (1)
Change History (4)
comment:1 follow-up: 2 Changed 10 years ago by
| Milestone: | 1.4 → tbd |
|---|---|
| Priority: | high → normal |
| Resolution: | → invalid |
| Status: | new → closed |
comment:2 Changed 10 years ago by
Replying to bill:
Please reopen after attaching a test case using the attach file button.
Why is this invalid? First - what is the normal behavior for a scrollbar and under what conditions does it appear or not appear? At least if that question is answered, I can try alternate methodologies to see what, if anything, I am doing wrong. Why is the onus always on the user to prove their point instead of trying to help them. I posted this to the email list, but as usual, you didn't bother to answer that.
comment:3 Changed 10 years ago by
your description is inadequate, which is why we request a test case be attached.
I, again, have taken the liberty of reproducing a test case based on your description. This ticket is still invalid as my test case clearly shows a ContentPane? with overflow:auto growing a scrollbar to accommodate the new textboxes (form elements) being added to the CP. This was tested with HEAD as of just now.
We cannot "see" what you are doing wrong if at all without a reproducible test case, which is why it is your responsibility to provide us one. If you want help, please provide some code to look at, not simply saying "this doesn't work" and expect someone to do the leg work for you.
If you find the community/free mailing list support inadequate, both SitePen? and Uxebu provide commercial prioritized support. You may find those options more accommodating.
Changed 10 years ago by
test case showing this working fine. please attach a new test showing otherwise before reopening.
Please reopen after attaching a test case using the attach file button.