#7414 closed defect (fixed)
Regression: FilteringSelect throws error on create()
Reported by: | haysmark | Owned by: | bill |
---|---|---|---|
Priority: | blocker | Milestone: | 1.2 |
Component: | Dijit - Form | Version: | 1.1.1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description (last modified by )
With the new attr changes, FilteringSelect no longer loads: http://archive.dojotoolkit.org/nightly/checkout/dijit/tests/form/test_FilteringSelect.html
Seems that create() calls setValue before MappedTextbox's valueNode is generated in postCreate.
Change History (4)
comment:1 Changed 13 years ago by
Description: | modified (diff) |
---|
comment:2 Changed 13 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
(In [14821]) Make MappedTextBox? do it's magic as part of buildRendering() rather than postCreate(). It's adding another node to the DOM so it really _should_ be part of buildRendering().
This fixes the FilteringSelect? initialization issue although it's still debatable whether all the attr() setter calls should happen before or after postCreate(), or inside _Widget.postCreate().
Also moved the attr() setter calls into a private method, in case that needs to be overridden.
comment:3 Changed 13 years ago by
comment:4 Changed 10 years ago by
Component: | Dijit → Dijit - Form |
---|
Yah, sorry about that. Perhaps the attr() calls should occur after postCreate() although that might cause other problems. Will investigate.