Closed GoogleCodeExporter closed 9 years ago
Why on earth would you create a new issue knowing that it's a duplicate!?
Comment on the existing issue!
This is a known issue. It's Chrome bug that passed through dev and is probably
in beta now. I can't do anything about it. Your data is all still there, it
will come back in the next version of Chrome (probably a day or two) Until then
there is nothing that can be done.
Original comment by anst...@gmail.com
on 2 Feb 2012 at 4:36
I'm sorry, but your explanation wasn't present in 133 and given the status of
133 and the justification for that status I wasn't confident that adding a
comment to that issue would draw any attention. I understand that you don't
want a mess in your issues list but I didn't see any way to change the status
and force the issue to be open again.
Thank you for explaining why it doesn't work. I will wait patiently for a new
version of Chrome.
Original comment by yitzchok...@gmail.com
on 2 Feb 2012 at 5:31
You can comment on closed issues. I will reopen closed issues if new evidence
arises that the issue is not resolved?
Original comment by anst...@gmail.com
on 2 Feb 2012 at 6:14
Original issue reported on code.google.com by
yitzchok...@gmail.com
on 2 Feb 2012 at 2:28Attachments: