Looks like we can't reproduce the issue or there's a problem in the test case provided.
Insufficient support for major bug fix
While trying to write my first app I came across a major bug with the sequence of the edit event parameters in version 4.0.7.
The parameters for the Chrome browser are in a different order then for the other browsers.
This to me is a major bug when my code will not work properly with one of the main browsers especially when the product claims compatibility across browsers as one of its main advantages.
My problem with the product is not so much that the bug exists but that Ext does not offer an immediate fix or workaround.
The notes states "Fixed in 4.1". Version 4.1 is in pre-release 1. Its not even stable or usable in production.
So to me this is unacceptable.
Ext should offer a fix of 4.0.7 or provide the workaround code.
I can understand that "paying" users get new features and improved features before "non-paying" users but fixing major bugs should be done for both otherwise it invalidates your claim and your product. Worst, it will reflect on the quality of my product if my users find it before I do.
Just read the 2nd half of your report. Yes, this is fixed in 4.1. However past releases are already finalized and sent out for the public to use. There are still bugs so that's why we still have a 4.1.0 and will continue to nail down bugs as we get reports and go through our bug tracker.
Basically you are saying that you do not fix bugs in current releases nor are you are offering workaround code.
So bugs of current releases, even critical ones, are only fixed in the next release which is some time in the future.
In the meantime, "paying" and "non-paying" users have to provide their own fix with no support for Ext.
On top of every thing I have to learn about using your products, I also have to learn how to identify the ext version and browser version I am using, in order to code my own workaround.
And people pay you for this privilege? Wow!
We do provide overrides to support subscribers. The bug you are talking about will be in the next release.
We obviously have different definitions for words like critical, urgency and support.
I was moving towards subscribing but I now I see that I would be wasting my money.
Why would you be wasting your money when I said we provide overrides for support subscribers?
I assume from your comment that what I called a "workaround" you call an "override".
Am I correct to infer that if I was to subscribe immediately, then within a few hours I would get the code that fixes the problem?
Would I also get the code that fixes all the other problems that have been found and fixed, and this without finding and asking for each one individually?
The way support works is depending on the level you get a response time and a certain amount of credits that each ticket would use. Depending on the level you pay for engineering would provide an override for the single problem you have.
Your answer to this is:
Originally Posted by rakagod
You did not answer this one:
Originally Posted by mitchellsimoens
Am I correct in assuming that the fixes would be in the SVN directory for development purposes. In other words all of the known fixes are in the latest SVN files that I can use to generate a personal "4.0.7a" version for continued development. Or are the SVN files at a 4.1 level with the fixes but also new features and such?
Originally Posted by rakagod
I did answer, I said you would get an override if you have the appropriate level of support for each ticket/issue. SVN has the latest code which is synced nightly, if you have the proper level. I do not believe 4.1 is in SVN as it constitutes quite a few changes... Not just bug fixes.