#33 closed defect (fixed)
widget parsing currently requires a parent
Reported by: | dylan | Owned by: | dylan |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | Widgets | Version: | 0.0 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
The current parsing of widgets needs some refactoring as it currently requires a parent node. I have a patch checked into webui/widgets/Parse.js, but it breaks other portions of the widget parsing system, especially programmatically added widgets, which needs cleanup on its own.
Change History (6)
comment:1 Changed 17 years ago by
comment:2 Changed 17 years ago by
Milestone: | → 0.2release |
---|---|
Version: | 0.2 → 0.0 |
comment:3 Changed 17 years ago by
Milestone: | 0.2release → 0.3release |
---|
comment:4 Changed 16 years ago by
Status: | new → assigned |
---|
comment:5 Changed 16 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Rearranged dojo.widget.Parse so the top level input fragment can be parsed as a widget.
I tested it against various invocations of createWidget. But there still might be something in Dylan's original warning.
If you want to have the old behavior, you should call
new dojo.widget.Parser().createSubComponents(frag, parentComp);
instead of
new dojo.widget.Parser().createComponents(frag, parentComp);
Is there any movement on this? How will it affect the APIs that are exposed to widget users and authors?