-
5 Sep 2012 12:06 AM #1
Ext.field.Slider at Google Chrome
Ext.field.Slider at Google Chrome
I don't know if it is the desired behavior or it's a bug. When using desktop Google Chrome (v.20.0.1132.57) @Ubuntu, the drop event updates the values with position of the mouse without taking on count the thumbs might be overlapped. So they can be both at the center of the screen (then they both should have 50 in this example) and if you get the one on the right side and try to move it to the left (dropping it at the 0) then the value of it is 0. At the UI they both are at the center (none has moved), but the shown values are (50,0).
Refered example: http://try.sencha.com/touch/2.0.1/de...bsOverlapping/
test case:
Code:Ext.create('Ext.form.Panel', { fullscreen : true, items : [ { xtype : 'toolbar', id : 'tbar', title : 'values = [25,75]', docked : 'top' }, { xtype : 'fieldset', items : [ { xtype : 'checkboxfield', label : 'allowThumbsOverlapping:', checked : true, listeners : { check : function () { Ext.getCmp('sl').getComponent().setAllowThumbsOverlapping(true); }, // check uncheck : function () { Ext.getCmp('sl').getComponent().setAllowThumbsOverlapping(false); } // uncheck } // listeners }, { xtype : 'sliderfield', id : 'sl', label : 'sliderfield:', minValue : 0, maxValue : 100, values : [25, 75], component : { allowThumbsOverlapping : true }, // component listeners : { change : function (slider, thumb, newValue, oldValue) { Ext.getCmp('tbar').setTitle('values = [' + slider.getValues() + ']'); } // change } // listeners } ] // items (fieldset) } ] // items (formpanel) }); // create()Last edited by mitchellsimoens; 7 Sep 2012 at 5:29 AM. Reason: added test case
-
7 Sep 2012 5:30 AM #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 33,582
- Vote Rating
- 433
I have opened a bug in our bug tracker for this as it happens on iOS Simulator also. IT makes the value wherever you let off of dragging, not where the thumb actually is.
You found a bug! We've classified it as
TOUCH-3415
.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.


Reply With Quote