Search:

When there's no service, and I send an http request, Chrome DevTools' Network panel shows a red entry with a status "(failed)". These requests normally triggered a requestexception prior to Ext JS...

I'm not Sencha personnel, so I can just share my perceptions about ExtReact, at least applied on the classic toolkit.

ExtReact on classic is far from being a fully featured React wrapper. It...

@dawesi, Thanks, I was unaware of this part. Sencha Cmd can be available inside our firm, however I need to initiate an onboarding process (internet is white-listed, and downloads don't work here)....

We don't have Sencha Cmd in the Firm (I guess for licencing reasons), but it's also a wise idea not to use ext-all/ext-all-debug, but just ext.js (or ext-debug.js and minify later). But this is a...

Pretty much a very frequent use case. And still not supported (in Ext JS 6)

I consider this a serious limitation, so to speak a conceptional bug.
It should work as it were containers inside...

A next layer of rounding seems to me solving the problem (in Ext.Number.toFixed):

(Math.round(Math.round(value * pow * 10) / 10) / pow).toFixed(precision)

Perhaps the issue is related to the fact that as per standard (though weird), 0.145 * 100 results in 14.499999999999998 (in every browser). Though IE handles (0.145).toFixed(2) correctly, resulting...

Repro is at https://fiddle.sencha.com/#fiddle/14m0

Ext version tested:
Ext 6.0.1


Browser versions tested against:
Chrome Version 47.0.2526.111 m

Did you even read the question? He said he wants to tie a component's viewmodel to an arbitrary other one, regardless of the dom or component hierarchy.

Here you are:

https://fiddle.sencha.com/#fiddle/10j8

Set fixIt to true in the first line to apply my possible fix for the issue.

Simple as it is in the title:

Ext JS 5+ column renderer is not called if a formatter is specified as well.

The docs doesn't say anything about it, and it's not trivial. My expectation is that...

Ext version tested:
Ext 4.2.2


Browser versions tested against:
All


DOCTYPE tested against:
not relevant

I agree, this is needed.

What a great answer. Thank you very much!

Thanks guys.

Ext version tested:
Ext 4.2.1


Browser versions tested against:
____ IE8 FF3 (firebug 1.3.0.10 installed) Safari 4


DOCTYPE tested against:
html

Fiddle updated: https://fiddle.sencha.com/#fiddle/227

Actually Object.create is enough instead of Ext.clone. Tabs just need a new reference inherited from the common tabConfig.

tabConfig in Ext.tab.Panel defaults breaks tabpanel's functionality. This bug is highly related to http://www.sencha.com/forum/showthread.php?244600, but that one is closed, and discussion there went...

It still shows:
//==========================================
// Ext JS Release Notes
//==========================================
// Release Date: February 24, 2008
// Current Version: 2.0.1...