-
10 Sep 2012 11:37 AM #1
Filefield remains disabled
Filefield remains disabled
Ext version tested:
- Ext 4.1.1
- Chromium 22.0.1231.0
- Firefox 15.0.1
- a filefield created initially disabled remains disabled forever. It works fine, just its style is like it was disabled.
- Create a filefield with config disabled: true
- In code, try to enable this field
- Now, the field is enabled but appears as disabled
- The field should be enabled
- the field remains disabled, but only in styles (you can select a file normally)
- only default ext-all.css
Code:Ext.create('Ext.panel.Panel', { renderTo: Ext.getBody(), height: 200, width: 320, bodyPadding: 10, title: 'Panel', items: [ { xtype: 'filefield', disabled: true, id: 'file' } ], dockedItems: [ { xtype: 'toolbar', dock: 'top', items: [ { xtype: 'button', text: 'Disable field', listeners: { click: function() { Ext.getCmp('file').disable(); } } }, { xtype: 'button', text: 'Enable field', listeners: { click: function() { Ext.getCmp('file').enable(); } } } ] } ] }).show();
-
10 Sep 2012 12:27 PM #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 34,107
- Vote Rating
- 453
In 4.1.2 the button does show as enabled however when you click on it it doesn't allow for you to choose a file.
I have opened a bug in our bug tracker.
Great test case!
-
10 Sep 2012 12:33 PM #3Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 34,107
- Vote Rating
- 453
Have this fixed for 4.1.3.
Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Forum Manager
________________
http://www.JSONPLint.com - Source to lint your JSONP!
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
https://github.com/mitchellsimoens
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services services@sencha.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is almost in print!
When posting code, please use BBCode's CODE tags.
Success! Looks like we've fixed this one. According to our records the fix was applied for
EXTJSIV-7204
in
4.1.3 Sprint 1.


Reply With Quote