Regarding forum posts (with support requests):

• Going on several years... no bug fix yet <--priority 1 red alert sirens blaring bug that takes down the entire website
• WebDataTree does not fire NodeClick when in WebSplitter
• WebDataMenu Itemclick event not firing

The first bug has taken down my core website twice in the last two days (and countless times over the years). All of my customers had to wait while I remoted in to do an IISReset.

Do you guys not get what that means? This one bug is repeatedly taking down the entire website, forcing me to restart the whole service. I am answering calls at 3:00AM to reset the site, while customers wait.  And it is evidently a low priority to you. It certainly didn't get fixed in this SR, or any SR in the last several years that people have been reporting it.

My customers' patience is officially exhausted. One customer has told me that unless I get this problem fixed, they are going to start underpaying my invoices. And seemingly, heaven, earth, and eons of time (literally years) will not move you to correct this critical bug. I have lost confidence that you will fix it *ever*, because it just isn't on your radar. you are too busy making icon packs.

I have no choice but to replace your chart control with another vendor. I am questioning my sanity for having stayed with the chart control for so long.  If you weren't going to fix critical bugs, why couldn't you just EOL the thing so that we would know what to expect?  

It is not just the chart control that has brought me to this point.  It is also your response to the new WebSplitter bugs.

I have been with Infragistics for years, but in the last two days, bugs have forced me to remove multiple instances of two of your controls from my website, while I scramble for replacements. The chart control, and the websplitter.  The websplitter is a big undertaking because I have used it a lot for layout.  However, new critical bugs introduced in this SR cause the websplitter to block events from your menu and tree controls., all three of which I use extensively. A container control that impairs child controls is critical.  I have lost a lot of time this week because I had to go to a bunch of my pages, remove the websplitter, and reformat the screen with fixed <divs>.

That's what I am having to resort to to work around your bugs. Replacing your controls with <divs>.

I honestly don't mind working around your bugs if you guys were committed to promptly releasing fixes.  But, shockingly, I have been told that the WebSplitter issue will not be fixed until the next SR.  I am stunned.  Stunned.  Stunned.  When I heard that, I was speachless.  Your solution to this bug is to ask me to turn my website upside down (with my sleep schedule) to quickly remove the WebSplitter and then to make due without it until the next SR.  And then, when you finally release a fix, you have the gall to expect me to trust the WebSplitter again, and go through all the work to re-implement it into my pages?  How am I to know that the same thing won't happen with the next SR with any of your other controls?

Is the Tab control next?  Am i going to have to replace all my Tabs with iframes for a month because you have a SR schedule?  Far-fetched?  That's exactly what I am having to do with the websplitter, and you are ok with it.

I do not expect bug-free controls.  but I do expect you to correct bugs quickly.  These are not feature requests.  These are bugs, and critical bugs at that.  A SR cycle is too long to wait for critical bug fixes.  But I understand.  You have icons to gather for your icon packs.

I am really annoyed to see all of this new development for jQuery and WP7 and icon packs and a new samples browser, while I struggle with bugs and simple documentation for the controls that I use daily.., Controls that I thought you were committed to. There is a balance between market dominance and quality. I feel strongly that the controls I use every day suffer because you insist on having a control for every purpose for every shiny new platform.  You are suffering in depth and quality because of your desire to be everywhere. Pick a market and excel at it. If ASP.Net is not that market, let me know so I can look elsewhere.

How long has the WebDataGrid been out?  While you are building *yet another HTML grid control*, WebDataGrid users are still waiting on features that were in the UltraWebGrid.  I still have UltraWebGrids that I can't upgrade because of missing features. 

I have news for you... My next grid will not be your jQuery grid. I believe that your jQuery grid will never be a mature product.  Here is why... Before you can build the power features that will make the jQuery grid a really dazzling, full-featured, mature product, you will shift your development priority to the next shiny new platform, just as you have done with WebDataGrid.  Just like WebDataGrid, the jQuery grid will never see multi-column headers or size-to-fit columns, because you will be busy writing a new HTML5CanvasGrid, or something else.

Guys, I am not quite ready to pull the trigger and drop your product line yet... I have invested too much, and have been too loyal for too long. Replacing your controls would be a massive undertaking.  I want you to redeem yourselves so that i can sing your praises again.  But you have burned me badly twice this week.  You have planted a huge seed of doubt.  The last several days have stretched the limit of my patience (and ability to go without sleep), and unless you get your act together, I will have to consider other vendors.

Don't bother fixing these specific bugs.  Let's be honest... you were never going to fix the chart bug anyway.  Further, you taught me a valuable lesson about trusting your container controls.... a mistake that I won't make again. I am now seeking replacements for the WebSplitter and WebTab controls.  These bugs are not my problem any more.

As a matter of integrity, you should be fair to your potential customers and EOL the chart control.  You need to remove it from your product offering if you are not going to fix long-standing bugs so severe that they will actually lock up a website.

You guys can be really terrific technically.  Some of your stuff is brilliant.  But my customers and my family don't want to hear how brilliant you are while they are waiting for me to work around the bugs that you won't fix.  I can't believe that I have come to this point.