maqetta/maqetta — Issue #1623: Investigate why comboEdit behaves differently than other widgets in WidgetProperties.js
Author: aerwin
Created: 2012-01-20 21:10:30+00:00
State: open

Opening based on @jhpedemonte comment on WidgetProperties.js in this commit: [https://github.com/maqetta/maqetta/commit/513030772447082e4a8bfff5c8931a080d53bd9b#L28R848]

```javascript

+ //NOTE: This comment was present here and the "var widget..." and "if(!widget){" lines
120
+ //were commented out:
121
+ //
122
+ // FIXME: Probably can remove commented out code, but leaving
123
+ // it in for now in case there is a case where widget==null
124
+ // The way things are coded now, widget is always null
125
+ //
126
+ //HOWEVER, I found a case where the assumption widget would always be null is _wrong_. The
127
+ //case is when the property is unconstrained and a comboEdit is in place. So, I've uncommented the
128
+ //aforementioned lines.
129
+ var widget = dijit.byId(this._pageLayout[i].id);
130
+ if(!widget){
```

```
I think the issue here is why widget is coming in as undefined. Rather than uncommenting these lines, I think it's better to fix the situation you referenced in the HOWEVER comment.

Fine to check this in for now, but please open a bug and track this down for M5, if you can.
```