Oliver reached out to me to let me know about the discussion here. Really appreciate that, thanks!
OK, so it probably helps to tell the whole story so you see where I'm coming from. Apologize for the length…
I work on the Chrome team so I wanted to help communicate about this change
. It's a big and contentious change. I myself don't like it and apparently a bunch of users don't like it either. When they don't like it, they go googling for information on how to fix it.
StackExchange sites are pretty much the perfect search result for people looking for answers; they're up-to-date, community maintained and are on the bleeding edge.
So I think it makes sense to have some knowledge shared on this platform that is more authoritative than some of the guesses, hacks, and this-is-what-i-figured out answers. I'm not admonishing those answers, and in fact, I leave them too. But it's awfully nice when you can get more context and a fuller answer.
Previously I've done this before by way of a self-answered question. It's a really effective means of communicating about an unwanted change: https://stackoverflow.com/q/18365315/89484
I wanted to do the same thing on this issue because people are confused, googling for help and trying to understand what's going on. This information is available in Chrome's user forums, but they're hardly discoverable for most people. So I added a self-answered question to superuser: What's the new user menu in Google Chrome?
It was closed as a duplicate, and I saw a variant of the question had already been asked before.
So why did I edit the existing accepted answer instead of adding a new one?
First up, multiple answers that are voted separately obviously imply they are competing answers. What I had to share didn't compete with the existing answer; it was including additional information and resources. This appears to be inline with the editing guidelines.
To be specific to this Chrome UI issue, people will be searching for a fix because of three reasons:
- they don't use profiles and don't need this
- it's slower than before and that sucks
- it's in an weird error state and communicating unclearly.
They sound pretty distinct concerns here as I spell them out but to users all three start with a search of
how disable chrome profiles button. So it feels unfortunate to give all three audiences the same answer that addresses 1/3 of the issue.
In the end, I feel my edit preserves the value of the original one and only augments it. I actually clarified the original answer, by spelling out the common mistake of not hitting "Restart" at the bottom (believe me, everyone misses it).
Policy-wise: I wasn't able to file this as a separate issue, which kinda makes sense (depending on how you look at it). I also appear to have satisfied the guidelines that "Edits are expected to be substantial and to leave the post better than you found it.".
Hope that helps explain what I was thinking.