Thank you for taking the time to respond, and I’m sorry you feel that way. I’m very appreciative of the work you guys are doing, and while I’m not trying to sound ungrateful or confrontational, it’s disheartening as an early user of the Ionic/React framework to see issues like this (https://github.com/ionic-team/ionic/issues/17679) go unanswered for months or, in that specific case, almost a year, with the only update happening when the issue is closed without resolution. This is not an inconsequential feature request or bug; promised support for browsers is quite big. To be clear, we are building an enterprise SaaS platform, so my concern is not our IT department, but rather the IT departments of all of my potential customers, about 20-25% of which are still using IE/Edge.
What I said about having spare time and cash (congrats, by the way) was not a snide remark at all, quite the opposite. As a founder myself, I can appreciate the heavy demand your team must have been under to prioritize carefully. Capital helps a lot with this, and my hope was that this issue is something that could be given a little attention now that you have room to breathe.
My company has sunk a lot of time into the Ionic/React framework, from beta 0.0.4 until now, under the assumption that the compatibility list would eventually be accurate. You and I have also had a Slack chat about this where you indicated that there should be compatibility with Edge and that you would look into it. Not placing blame, just indicating that this recent shift towards ignoring that issue (as indicated in GitHub) was very unexpected and, if we had known, we may not have chosen to use that framework due to the massive impact a lack of browser support has on our potential market.
I hope you can see where I am coming from with more clarity. While this is a major issue for me, I still appreciate the work you guys are doing on the other aspects of the platform!