#733 closed defect (invalid)
SplitContainer with ContentPane loaded by href, resize bar has not a good size
| Reported by: | Owned by: | neil | |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | Widgets | Version: | 0.3 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description
The resize bar has not the good size after loading ContentPane? from href.
SplitContainer?.paneWidth and SplitContainer?.paneHeight must be rebuilt after load.
Same problem when the ContentPane? overflow the SplitContainer? on resizing.
Attachments (7)
Change History (15)
comment:1 Changed 14 years ago by
| Milestone: | 0.3.1 → 0.4 |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
| Version: | → 0.3 |
Changed 14 years ago by
| Attachment: | test_split1.html added |
|---|
SplitContainer? and ContentPane? loaded externaly
comment:2 Changed 14 years ago by
| Resolution: | invalid |
|---|---|
| Status: | closed → reopened |
comment:3 Changed 14 years ago by
You can see it here: http://arneodo.perso.cegetel.net/dojo-cap-root/test_split1.html
comment:4 Changed 14 years ago by
| Owner: | changed from anonymous to bill |
|---|---|
| Status: | reopened → new |
comment:5 Changed 14 years ago by
| Owner: | changed from bill to neil |
|---|
Changed 14 years ago by
| Attachment: | splitcontainer_733_test_ie.html added |
|---|
splitcontainer_733_test_ie.html, testcase for ie/FF browsers no patches necessary, see comments
Changed 14 years ago by
| Attachment: | splitcontainer_733_test_ff.html added |
|---|
splitcontainer_733_test_ff.html, testcase for applied patches to be used with the FF browser form the $DOJO_ROOT/tests/widget directory, see comments
Changed 14 years ago by
doc1.txt and lorem-ipsum-long.txt, bogus text files used to fill contents of Content pane for execution with testcases supplied.
Changed 14 years ago by
| Attachment: | lorem-ipsum-long.txt added |
|---|
doc1.txt and lorem-ipsum-long.txt, bogus text files used to fill contents of Content pane for execution with testcases supplied.
Changed 14 years ago by
| Attachment: | SplitContainer.js.patch added |
|---|
SplitContainer?.js.patch, patch for src/widget/SplitContainer.js
Changed 14 years ago by
| Attachment: | HtmlWidget.js.patch added |
|---|
HtmlWidget?.js.patch, patch for src/widget/HtmlWidget.js
comment:6 Changed 14 years ago by
SplitContainer?.js.patch, patch for src/widget/SplitContainer.js HtmlWidget?.js.patch, patch for src/widget/HtmlWidget.js
testcases: splitcontainer_733_test_ff.html, testcase for applied patches to be used with the FF browser form the $DOJO_ROOT/tests/widget directory splitcontainer_733_test_ie.html, testcase for ie/FF browsers no patches necessary
datafiles: doc1.txt and lorem-ipsum-long.txt, bogus text files used to fill contents of Content pane for execution with testcases supplied.
There exists a patch for FF browsers. In this patch, rework was conducted on the postCreate and onRefresh methods of the SplitContainer?.js widget. The postCreate was delayed by adding to the onLoad calls (enabling the browser to correctly render the testcase), and the onRefresh reflects calculation of dimensions based upon the SplitPane?. Under this condition, the bounding box of the SplitContainer? need not be fixed. Elements filling the bounding box determine the dimensions of the rendering of the sizer bars.
The method listed above did not successfully render using the ie browser. For this case, the testcase had to explictly define all position attributes.
Testcases are available for both. For the ie testcase, it is independent of the patches supplied for the SplitContainer?.js and HtmlWidget?.js. For the FF testcase, both patches must be applied to successfully render.
comment:7 Changed 14 years ago by
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
OK, I talked to Neil about this one. Basically the problem is that you didn't specify a height for your SplitContainer?. You need to do that. See splitcontainer_733_test_ie.html (3.4 kB) - added by neil on 09/15/06 22:22:57
Many of the demos have content panes loaded by href (like Mail.html or Panes.html), so I think this is working in general. Look at those demos and see if you are doing something differently. If necessary, please reopen the bug with a testcase.