[by pierresas]

Thanks for the report! I have opened a bug in our bug tracker.

[by pierresas]

@Qtx: I tested with 4.2 but the fix is still valid. I checked under all 4 themes (Accessibility, Classic, Grey, Neptune) to make sure the CSS was correct too.

Have you updated your button handler?...

[by pierresas]

Here is a solution that's not as simple as using the missing 'reverse' config but it works in ExtJS 4.2.
It consists in...
- Providing a convert() function in the model that returns negative...

[by pierresas]

In extjs/src/util/Floating.js, function toFront(), do:
me.focus(false, false);
instead of:
me.focus(false, true);

The fix did not make it into 4.1.3 for lack of testing, so please use...

[by pierresas]

Sorry, it was a mistake. The fix did not make it into 4.1.3.

[by pierresas]

The bug number that was assigned to this issue is EXTJSIV-6879.
Please provide a test case and we will reopen the bug.

[by pierresas]

This bug report was closed as Incomplete because after 2 requests, the customer still did not provide a test case nor additional explanations.

It looks like the chart is drawn using an unstacked...

[by pierresas]

@jjerome The 'fill' config was always required. You can verify it by downloading 4.0.7 from http://www.sencha.com/products/extjs/download/ext-js-4.0.7 and opening examples/charts/Mixed.html: if you...

[by pierresas]

@london_lawyer: The bug was marked "fixed" because the only functional test case was incorrect and has been fixed. Five other users in addition to yourself have reported an issue but they did not...

[by pierresas]

Five users (Dev.init, RFman, matiou, vasily_87, ynov) have not provided a complete test case and the issue could not be reproduced, so there is nothing we can do for them. The fix proposed by user...

[by pierresas]

@nightwatch - Please attach some sample code so we can investigate...

[by pierresas]

The test case is invalid. The code shouldn't be:
inputType:"file",

xtype:"textfield"
but instead...
xtype:"filefield"

[by pierresas]

The problem is in the sample code, not in the framework. By calling this.up('form').getForm().getFields(), you collect an array of all the individual fields that are sent back by the form. A field...

[by pierresas]

You are correct, it was a bit confusing. The code won't change but the documentation will be clarified:
--
The CSS class(es) added to the component's main element when it is in the checked state....

[by pierresas]

A fix will be available in 4.1.2. For those of you who have access to the code, the fix is at https://github.com/extjs/SDK/pull/7035

Thans you for the detailed bug report and the test case.

[by pierresas]

leon_tang,

A fix is ready and it will be available in 4.1.2. Column charts can now be bound to both the left and bottom axes when they are both numerical.

I don't know if you have access to the...

[by pierresas]

@leon_tang

The framework does support lines and columns in one chart; this is not the issue. The problem I see is: in the example you provided, the columns are always slightly off. It doesn't...

[by pierresas]

The number of ticks is 10 by default. You can set the 'majorTickSteps' config to 5 for instance, or to the maximum value in your data, and that should remove the decimal values along the axis.

[by pierresas]

There is still a bug that's revealed by your test case: the columns are not displayed at the correct location on the x-axis, but that's independent from displaying a 'line' series at the same time.
...

[by pierresas]

It doesn't appear to be a bug to me. Margins were added on both sides to draw the columns. If you remove the config "style: { 'width': 5}", it's clear what is happening.

[by pierresas]

@jclark42796 & @jclingen: There is an issue with iFrames and re-layouts in different browsers. For more explanations, see the docs at...

[by pierresas]

This was fixed in 4.1. Please let us know if you still see the issue.

[by pierresas]

Fixed in extjs/SDK/pull/6756

Scott.

[by pierresas]

@mashiki & @jvisser: Indeed, it can be reproduced very easily with the examples you provided. Thanks!

[by pierresas]

@jvisser: Thank you for giving us access to your JSFiddle testcase. I'll look into it tomorrow.

3 engineers here (one in support, one in QA and myself in Dev) were unable to reproduce the problem...