I can understand having rules, and as I said I totally understand wanting questions and general discussion in the forums. Redirecting such discussions to the forum and closing the issue for such things is totally fine, and doing so is also fine if it’s a case of just needing to read the docs.
And I’m disappointed when people just ignore rules we try to establish. So we are even
This isn’t a competition or fight, there’s no getting “even” here.
Wrong. They are marked as answered. Furthermore, every time we confirm a bug or anything that will lead to an issue, we reference it here and create an issue. So you can still look it up in Github if you need. So everyone is happy.
This system is clearly not strictly followed. There are many posts in this bugs forum not marked as solved, are they really all unresolved? This seems very unlikely (for example MASSIVE BUG: gizmo + rotationquaternion - #10 by mrlooi, a pr was made and merged, but forum topic was not marked as solved). Github issues are not always made, or a pr is made without an issue ever being opened (see previously linked topic). Issues easily become lost (such as MultiMaterial Solid Particle System Breaks Picking - #5 by jerome, for which no issue or pr seems to have been made, and has probably long fallen off the core teams radar).
I also can’t seem to find a way to filter topics by the solved state (if this functionality exists I’d love to be pointed towards it as it would at least partially address some of my concerns).
And we always look at the issue anyway (in order to not lose them).
I’m glad issues are still looked into, but without an open issue then I can easily see it being overlooked if not addressed immediately.
Let’s agree to disagree then as I already explained why we want only one channel to communicate with the community
Again I understand wanting to have one place people look for information, but bugs are not the same thing, and discussing bugs, referencing commits that might have introduced them, linking to code etc is far better served by tool that is designed for that purpose. At the very least using that tool (github) for that purpose shouldn’t be frowned upon.
@PolygonalSun Thanks for looking into this.
I thought the motivation would be something to do with unifying web and native controls, and can see why this would be desired.
I think the IE11 issue is slightly deeper than just getGamepads being undefined, as setting that to an empty array then exposes the other mentioned issue regarding mouse wheel.