Sorry, I wasn’t trying to say that it wasn’t getting fixed, etc. I wasn’t simply trying to express why workarounds are an absurd idea for this case, or why forcing my users to use the app is a no go in many situations. I felt I already expressed that why it wasn’t a solution in previous replies, as well as the fact that directing to the app is not a solution, nor should it even be implied as a solution for many reasons.
I’m not asking for features to be added, or fixed. I’m requesting for basic navigation to work correctly, there is a big difference. If this was a feature issue, I would understand workarounds, etc. As for use case, hardware etc., open.rocket.chat has had the same issues all this time. This isn’t a hardware, or setup issue, it’s an issue with rocket.chat code.
As stated before, I am not that kind of developer, and I have offered to pay someone over on github to fix it, with no response. To be honest, nobody should have to ‘fix it themselves’ when they aren’t the ones getting millions in funding, and you have paying customers. Like it or not, this is paid software with a revenue stream. Fixing basic navigational issues should not be put on the users that beta test the software for you and report the issues.
I agree that if I want a feature, I should add it myself, and if I choose to, share it. But core functionality should not be passed on to an end user who may or may not have the resources or knowledge to fix it, when Rocket Chat clearly should have the funds and resources to fix their own software when it comes to core functionality such as navigation.
Open source is great, and I appreciate the hard work Rocket Chat does and all it’s developers, but there is a line where Rocket Chat should not be saying “fix it yourself”, and core functionality that doesn’t even work on their own setup should be the line.
I’m looking forward to the fixes, thank you.