To be fair, the idiomatic phrase “red herring” does not always imply intent — I myself often use this phrase to describe facts that are not relevant to the context, without imputing any intent to distract.
Certainly you will agree (in retrospect) that the URI re-sorting feature is not relevant to this feature request. But I don’t think anybody (including @Phil_Church) believes that you brought this up with any intent other that to bring awareness to what you thought (at the time) would be a solution to the problem.
Well said. I think everyone is acting with good intentions, I hope I did not imply otherwise. Now if only getting the NOT operator implemented was as easy to resolve we would all be laughing.
This was a confusing experience today. I also found myself wanting to ignore autofill on a very specific subdomain. Allowing Never to override matching a specific subdomain is exactly the behavior I intuitively expected and would be preferred over writing regular expressions.
I agree, but suspect asking to change the established behaviour of Never is too much, far better IMO to ask to have a new NOT operator added. This would be a simple non breaking change that cleanly solves the problems we have discussed above.
Unfortunately even though the solution (using NOT) is simple, until we get hundreds of votes on this topic Bitwarden will not see it as a problem worth fixing.
