Yeah... the following (which I assume that you're referring to) > > Re #19, we understand that this was an undesirable decision for some users, but we sometime

Yeah... the following (which I assume that you're referring to) > > Re #19, we understand that this was an undesirable decision for some users, but we sometimes need to make a product decision like this. Chrome and Chrome OS strive for simplicity. Every feature comes with complexity. Complexity adds maintenance cost, QA cost, slows down development, and adds surface of security exploits (as mentioned in #12). We should add a feature only if its benefit clearly outweighs its cost, but this particular feature was slipped in for some historical reason. Sounds reasonable enough. But it could be used to justify pretty much anything.