I'm not keen on having it omitted, if they decide to put it in and it makes people happy, that's fine. I just have no use for it personally. But I'm not arguing from that perspective. I'm arguing from the perspective that adding new features costs time and money so it makes sense to evaluate each feature. And yes, this is a new feature, because this is a new browser. I know that's unfortunate for people who have come to rely on the old Edge and may now be faced with losing a beloved feature. But the fact is still, they'd have to implement it again, and it may be a feature (it probably is) that barely sees any use from people, so that makes it doubly challenging to justify allocating resources to it. If most people haven't been using it until now, is there any guarantee they would now? If there is a guarantee, is it still worth the time and money investment? Or could it maybe be that the only reason it was not used was discoverability and low use of Edge itself so if it gets implemented now and there turns out to be a compelling use case *for many people* (not just for the niche commenting here), could it actually become a successful feature? Those are all legitimate questions the Edge team is asking. All I'm saying is people should understand those questions and the fact that the Edge team is facing them. You on the other hand say, it's an existing feature on old Edge and people here are asking for it to be added, so that alone is sufficient reason for Microsoft to do the work, but I think you need to understand that is not the case, even if it means you may lose a beloved feature (and I understand that hurts, I really do).
