Is it really a good idea to mark this well-described bug as a duplicate of something that just describes a solution?
I find one of the most valuable things we can do to propel the community forward is to have accurately described bugs so people can get together and discuss the same issue (even after a fix becomes available). But by marking this as a duplicate of bug 1637520, that can't happen.
Is it really a good idea to mark this well-described bug as a duplicate of something that just describes a solution?
I find one of the most valuable things we can do to propel the community forward is to have accurately described bugs so people can get together and discuss the same issue (even after a fix becomes available). But by marking this as a duplicate of bug 1637520, that can't happen.