This doesn't mean users have to operate Jama with no browsers enabled or safe mode on, but it does mean if a problem comes up that we aren't reproducing here, then browser add-ons have to be looked at as a potential cause. We have to balance updating features and fixing bugs with needed regression cycles, and we don't want to make regressions longer, so it's these sort of situations where we have to say, " x is not supported." And if we don't test it, we can't say it's supported.
It is too much overhead to add another variable to our testing. Obviously not all extensions conflict with Jama, and that's the problem-we can't test every interaction that an extension might have with Jama. But to answer your first question, no, I personally do not disable my extensions when I run Jama. Vladimir, I understand where you're coming from, and I know what you mean about how the users will react.
0 kommentar(er)
