(In reply to comment #324) We should avoid discussing closure of this bug until we can verify that the new implementation has been included in a released build and that it no longer suffers from the issues reported here.
(In reply to comment #324)
We should avoid discussing closure of this bug until we can verify that the new implementation has been included in a released build and that it no longer suffers from the issues reported here.