@DavidGB I understand your frustration, I'm a user of my own product, and there are still features that I'm waiting for that make it very difficult to use in the meantime (in my case, I use lots of tabs, so having them squish down to an itty bitty size makes it almost impossible for me to figure out which one I need at any given time).
The problem is that nobody can give you a definitive answer because there are no definitive answers. I'm never going to say something will never happen, because never is a long time, and we don't plan on stopping or slowing down development any time soon. Everything is just a question of priority: how many users are asking for something, how bad the problem is that needs to be solved, what workarounds there are, how hard is it to deliver, what do our competitors offer, etc. And in my years on the browser team, I've learned that everybody has that one "killer" feature that they absolutely need, and rarely is it the same as anybody else's killer feature.
So, as we continue to finish up the features we're working on, we constantly re-evaluate our priorities and decide what to work on next. And if that comes off as being non-committal, I apologize, that's not the way we want it to seem. It's just hard for us to say "well, we think we'll be able to get to it in 6 months" when we don't know what other priorities are going to come up in 6 months once our current set has been delivered. Maybe Google is working on this in Chromium and we'll just get it for free. Maybe it's actually really hard to implement in Chromium's codebase and we won't know that until we start working on it. In the meantime, yes, helping us understand why it's important to you does help us, especially when you tell us why it's so necessary, not just that it is.
