Opened 14 years ago
Closed 14 years ago
#3585 closed defect (fixed)
test_LayoutCode.html not working
| Reported by: | bill | Owned by: | Adam Peller |
|---|---|---|---|
| Priority: | high | Milestone: | 0.9 |
| Component: | Dijit | Version: | 0.9 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description
Pressing most of the buttons (at least on IE6) causes one error or another. Need to fix this to test new _destroyElement() function (#2931)
Change History (9)
comment:1 Changed 14 years ago by
| Owner: | changed from bill to Adam Peller |
|---|
comment:2 Changed 14 years ago by
comment:4 Changed 14 years ago by
| Milestone: | 0.9beta → 0.9 |
|---|---|
| Priority: | normal → high |
1) the simplelayout results are different from 0.4.x -- top doesn't stretch from left to right. bug or feature? 2) splitpane and tab layout throw an exception, I think because layout is called the wrong time when children are added after construction 3) the current widgets panel gets longer and longer with each iteration. it didn't used to.
comment:6 Changed 14 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:7 Changed 14 years ago by
bill says the simple layout changes are due to a change in 0.9 regarding the layoutPriority flag. Everything else is fixed, more or less. We'll track any new issues in a separate bug.
comment:8 Changed 14 years ago by
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
This still isn't working for Bill. Just press "Simple Layout" followed by "SplitContainer?". I get an exception in firebug because Split Container::addChild() is calling layout() before startup(). Must be in IE.
comment:9 Changed 14 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
old copy. it works fine, apparently.
OK, I'm gonna checkin the _destroyElement() changes before this gets fixed, so after fixing please make sure that everything works w/out error on IE6. Actually should check if there is still a memory leak on IE6. (Press the buttons repeatedly and watch if the memory usage of IE goes up without limit.)