Well, Angelo, I think the questions are: Why is it desirable to leave it the way it is? If it's preferable to change it to normal, intuitive behavior, how difficult is it? If the behavior is changed, will that make future improvements easier or more difficult, and by how much?
It's not unintended behavior, so it's not clearly a bug, but if we were to weigh it, I can't help but think the balance would indicate "bug" instead of "feature."
[Insert my standard rant about defining "bug" as something that disappoints the customer instead of something that the programmer didn't intend.]
Cheers - Bob
Sophos UTM Community Moderator Sophos Certified Architect - UTM Sophos Certified Engineer - XG Gold Solution Partner since 2005
Well, Angelo, I think the questions are: Why is it desirable to leave it the way it is? If it's preferable to change it to normal, intuitive behavior, how difficult is it? If the behavior is changed, will that make future improvements easier or more difficult, and by how much?
It's not unintended behavior, so it's not clearly a bug, but if we were to weigh it, I can't help but think the balance would indicate "bug" instead of "feature."
[Insert my standard rant about defining "bug" as something that disappoints the customer instead of something that the programmer didn't intend.]
Cheers - Bob
Sophos UTM Community Moderator Sophos Certified Architect - UTM Sophos Certified Engineer - XG Gold Solution Partner since 2005
I would consider this a bug. Using the browser button should have the same effect as using the button in the UI. Isn't the UI button a workaround for the real issue?
