[3.x] Ext.ux.form.SuperBoxSelect

[abraxxa]

When calling isValid in the superboxselect component firebug reports a 'too much recursion' error.
It can be fixed by removing the clearInvalid calls in validateValue.
ExtJS itself doesn't call clearInvalid in validateValue either (for example in Ext.form.NumberField), so I assume this is the correct fix for the problem.
If not please correct me.

validateValue: function(val){
        if(this.items.getCount() === 0){
             if(this.allowBlank){
                 /*this.clearInvalid();*/
                 return true;
             }else{
                 this.markInvalid(this.blankText);
                 return false;
             }
        }
        
        /*this.clearInvalid();*/
        return true;
    },

[rdblyth]

SuperBoxSelect is giving me issues in IE7 after I added a doctype for HTML 4.01 Transitional. If the superboxselect is empty and I peform a search results come back fine and I can select them. If I perform another search after I have one item in my superboxselect the results are not displayed and my search term disappears. If I remove the doctype everything works great. The odd thing is sometime this problem occurs after having one item or two items in the superboxselect.

Firefox works fine either way.

Has anyone seen this problem. Any help would be appreciated.

Thanks
Daniel

[rdblyth]

SuperBoxSelect is giving me issues in IE7 after I added a doctype for HTML 4.01 Transitional. If the superboxselect is empty and I peform a search results come back fine and I can select them. If I perform another search after I have one item in my superboxselect the results are not displayed and my search term disappears. If I remove the doctype everything works great. The odd thing is sometime this problem occurs after having one item or two items in the superboxselect.

Firefox works fine either way.

Has anyone seen this problem. Any help would be appreciated.

Thanks
Daniel

After trying to debug the problem it looks the problem is caused by the SuperBoxSelect losing focus. When the problem occurs if I click outside of the SuperBoxSelect and then back then the problem corrects itself, but will come back after adding a few more items. Also If I use the keyboard and not the mouse to add items I don't get the problem.

[jmiguel]

Very nice component!

I am trying, but when I disable+hide it and then enable+show, the list of the elements changes it's width to a very small one...

To hide/show it I use:

field.hide();
field.show();

This is my implementation:

var sbs = new Ext.ux.form.SuperBoxSelect({
msgTarget: 'under',
allowAddNewData: true,
id: name,
fieldLabel: 'test',
emptyText: '',
resizable: true,
name: 'mytest',
anchor:'90%',
store: mystore,
mode: 'local',
displayField: 'name',
valueField: 'id',
extraItemCls: 'x-tag'
});

Any idea??

Great component!
Regards

[abraxxa]

That happens too when the superboxselect is inside a collapsed or hidden panel after it's expanded/shown.
I'd need a fix for this too.

[jarlau]

Hi Dan,
I ran into 'this.store is null' error in onStoreLoad() when the second form creates(the first form has no problem).
But the problem solved if I changed all 'this.store' to 'store' in the entire function. Is it ok to do such change?

rgds,
Jarlau

[jmiguel]

That happens too when the superboxselect is inside a collapsed or hidden panel after it's expanded/shown.
I'd need a fix for this too.

Solved, I removed the anchor and used a fixed width (loosing some functionality..., but it works)

---anchor:'90%',
+++width: 450,

[abraxxa]

Doesn't fix anything here.

[nmohler]

SuperBoxSelect is giving me issues in IE7 after I added a doctype for HTML 4.01 Transitional. If the superboxselect is empty and I peform a search results come back fine and I can select them. If I perform another search after I have one item in my superboxselect the results are not displayed and my search term disappears. If I remove the doctype everything works great. The odd thing is sometime this problem occurs after having one item or two items in the superboxselect.

Firefox works fine either way.

Has anyone seen this problem. Any help would be appreciated.

Thanks
Daniel

I have seen a similar issue using the same doctype declaration. Removing the doctype eliminates the poor behavior, but introduces even bigger problems in other areas of the app.

I see the behavior in two scenarios:
1) The SuperBoxSelect is populated while the SuperBoxSelect is in a scrollable container and the SuperBoxSelect is not visible.
2) I cause the "blur" event while the SuperBoxSelect is in a scrollable container and the SuperBoxSelect is not visible. For example, scroll the SuperBoxSelect into view, click into the component, scroll so the SuperBoxSelect is not visible, and then click into open space or another component.

In both cases, the SuperBoxSelect jumps to a different area within the scrollable container, typically overlaying another component.

I would appreciate any help as I'm pretty stumped on this one.
Nick

[nmohler]

I have seen a similar issue using the same doctype declaration. Removing the doctype eliminates the poor behavior, but introduces even bigger problems in other areas of the app.

I see the behavior in two scenarios:
1) The SuperBoxSelect is populated while the SuperBoxSelect is in a scrollable container and the SuperBoxSelect is not visible.
2) I cause the "blur" event while the SuperBoxSelect is in a scrollable container and the SuperBoxSelect is not visible. For example, scroll the SuperBoxSelect into view, click into the component, scroll so the SuperBoxSelect is not visible, and then click into open space or another component.

In both cases, the SuperBoxSelect jumps to a different area within the scrollable container, typically overlaying another component.

I would appreciate any help as I'm pretty stumped on this one.
Nick

In digging through this problem, it appears that it occurs when the SuperBoxSelect is within a container using the "Fit" layout. The problem goes away when I remove the "Fit" layout and size the container component using the height and width config options.

I'm still digging to determine why "Fit" creates an issue...