-
7 Mar 2012 8:21 AM #1
dirtyCls style not applied to slider field
dirtyCls style not applied to slider field
REQUIRED INFORMATION
Ext version tested:
- Ext 4.1.0 Beta 2
Browser versions tested against:
- Internet Explorer 9.0.8.16421
- Firefox 9.0.1 (Firebug 1.9.0)
- Chrome 16.0.912.75m
- Safari 5.1.2 (7534.52.7)
- Opera 11.60(build 1185)
DOCTYPE tested against:
- <!DOCTYPE html>
Description:
- The dirtyCls CSS style is not applied to the label of a slider field
Steps to reproduce the problem:
Using the sample below:
- Change the value of the text field and note that the style of the label changes
- Change the value of the slider field and note that the label does not change
The result that was expected:
- The style of the slider label changes to match the style specified in the dirtyCls class
The result that occurs instead:
- The style of the slider label does not change
Test Case:
Code:<!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <title>Dirty Slider bug report</title> <link rel="stylesheet" type="text/css" href="ext/resources/css/ext-all.css"/> <script type="text/javascript" src="ext/ext-debug.js"></script> <style type="text/css"> .dirty-field { color:DarkOrange !important; font-style:italic !important; } </style> <script type="text/javascript"> Ext.application({ launch: function () { Ext.create('Ext.container.Viewport', { layout: 'border', items: [{ region: 'center', xtype: 'form', items: [{ xtype: 'textfield', name: 'mytext', fieldLabel: 'text label', value: 'text value', dirtyCls: 'dirty-field' }, { xtype: 'sliderfield', name: 'myslider', fieldLabel: 'slider label', width: 300, minValue: 1, maxValue: 100, value: 50, dirtyCls: 'dirty-field' }] }] }); } }); </script> </head> <body></body> </html>
HELPFUL INFORMATION
Debugging already done:
- none
Possible fix:
- not provided
Additional CSS used:
- ext-all.css
- custom css class 'dirty-field' specified in sample
Operating System:
- Windows 7 x64
-
7 Mar 2012 11:49 AM #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 33,656
- Vote Rating
- 435
Thanks for the report.
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.
-
3 Apr 2012 3:53 AM #3
So I noticed that 4.1 RC1 is out but this isn't listed in the release notes for it. Does this mean it's not likely to be fixed for 4.1 at all or is there an intended RC2 that might contain it?
-
3 Apr 2012 3:54 AM #4Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 33,656
- Vote Rating
- 435
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.
-
4 Apr 2012 12:00 AM #5
I've just seen the new blog post announcing RC2 and this item is listed as fixed. I guess this page just wasn't updated.
Success! Looks like we've fixed this one. According to our records the fix was applied for
EXTJSIV-5546
in
4.1.


Reply With Quote