-
15 Dec 2012 5:51 AM #1
Ext.utils.CSS.getRule - always throws error
Ext.utils.CSS.getRule - always throws error
nice refactoringCode:getRule: function(selector, refreshCache, rawCache) { var i; if (refreshCache) { CSS.refreshCache(); } if (!Ext.isArray(selector)) { return rawCache ? rules[selector.toLowerCase()] : rules[selector.toLowerCase()].cssRule; } for (i = 0; i < selector.length; i++) { if (rules[selector[i]]) { return rawCache ? rules[selector[i].toLowerCase()] : rules[selector[i].toLowerCase()].cssRule; } } return null; },
it ALWAYS throws an error.
rules variable comes from!?
I think the developer forgot a line like:
var rules = this.getRules(refreshCache);Management means doing the things right,
Leadership means doing the right things.
www.interpid.eu, www.webdbadmin.com
-
15 Dec 2012 5:56 AM #2
This solution works(at least for my cases)
Code:getRule: function(selector, refreshCache, rawCache) { var rules = this.getRules(refreshCache), i; if (refreshCache) { CSS.refreshCache(); } if (!Ext.isArray(selector)) { return rawCache ? rules[selector.toLowerCase()] : rules[selector.toLowerCase()].cssRule; } for (i = 0; i < selector.length; i++) { if (rules[selector[i]]) { return rawCache ? rules[selector[i].toLowerCase()] : rules[selector[i].toLowerCase()].cssRule; } } return null; },Management means doing the things right,
Leadership means doing the right things.
www.interpid.eu, www.webdbadmin.com
-
15 Dec 2012 10:11 PM #3
Thanks for the report! I have opened a bug in our bug tracker.
-
16 Dec 2012 4:35 AM #4
Fixed method:
Code:getRule: function(selector, refreshCache, rawCache) { var i; if (!rules || refreshCache) { CSS.refreshCache(); } if (!Ext.isArray(selector)) { return rawCache ? rules[selector.toLowerCase()] : rules[selector.toLowerCase()].cssRule; } for (i = 0; i < selector.length; i++) { if (rules[selector[i]]) { return rawCache ? rules[selector[i].toLowerCase()] : rules[selector[i].toLowerCase()].cssRule; } } return null; },Search the forum: http://www.google.com/coop/cse?cx=01...%3Az7of1ufqccu
Read the docs too: http://extjs.com/deploy/dev/docs/
Scope: http://extjs.com/forum/showthread.ph...642#post257642
Success! Looks like we've fixed this one. According to our records the fix was applied for
EXTJSIV-8042
in
4.2.0 Sprint 2.


Reply With Quote