Champion Level 3Hi @awaldo
If you reread the post from larebshaikh, you'll see that they are saying they have already implemented what I suggested, not that I said anything was implemented nor that I am hiding anything. Since I don't work for SmartBear, I would not be the first one to hear about changes anyway. I have, however, seen items on the Feature Requests list be implemented.
The behavior you described in the posts is what normally goes on here. Volunteers like rraghvani and I spend time on the forums to offer our expertise and we are happy to keep discussing issues, with no "stop talking about it" implied. What usually happens, even if we try to follow up, is that the original poster disappears.
If the workarounds are not sufficient to keep the user's work progressing, then there is always the option of logging an issue with Support.
I think you will find that most testing teams have different requirements and different environments and no one is testing anything exactly the way or for the same purpose as anyone else. They will also choose tools and design tests that fit them the best.
I wish you luck in testing with your new framework.
You're right, I misread the wording of their comment and didn't understand what was going on exactly
I agree with your assessment though, this is how public forums like this usually work, it's completely normal. I was trying to say something like that in my response as well, that it seems like in general people using this product aren't bothered by the problem like the two of us are and so it's not an issue on the whole. It doesn't exactly help us though, since the proposed solution causes more problems than it's worth, and separating the header elements into a separate project doesn't help us use them in our tests to navigate/login/etc, so it doesn't really help (for my case anyway).
