Closed GoogleCodeExporter closed 9 years ago
Affects the Google Chrome version as well.
Original comment by ja...@jamesrgifford.com
on 4 Apr 2011 at 9:16
yea..it also affect chrome version!
Original comment by amithsv...@gmail.com
on 4 Apr 2011 at 9:29
can you describe more details? I cannot reproduce it
Original comment by 5h3l...@gmail.com
on 5 Apr 2011 at 2:50
Here's how I reproduced the problem. However, I had to try about 10 times
(exact same steps) to get it to happen.
I selected the "Message user" option from a tweet, then wrote my message. I
needed a link, so I switched to another tab. Once I got back to the tab with
Hotot in it, I pasted the j.mp link into the tweetbox, hit send, and it was
posted to the timeline instead of being sent to the account I was intending it
to be sent to. Chrome 12 Linux.
Original comment by ja...@jamesrgifford.com
on 8 Apr 2011 at 11:13
I've got the same behaviour with v. 0.9.6, in Ubuntu 10.10 x86x64. Everitime I
replied to someone's DM, I hit the envelope icon accompanyng the DM I want to
reply to. The composing window showed up, but the recipient field showed itself
empty. When I Updated, received the warning that I had to specify a recipient
for the DM (wasn't this a reply to a DM? Don't have to). Did specify the
recipient, and when updated, DM showed up in the public timeline. Fact is that
this updated version, from the Ubuntu repositories, is got this bug, not
present in the previous version.
Original comment by mando...@gmail.com
on 19 Apr 2011 at 3:55
Hello,
I think this bug has been fixed in rev777:8576ee8adc02.
Original comment by 5h3l...@gmail.com
on 24 Apr 2011 at 6:56
This bug is still present in the Chrome plugin as of today. I was unaware of it
until someone asked why I was reposting all my DMs to them in the public
timeline.
I would suggest raising the priority on this to high. Users that are unaware of
the bug could reveal critical personal info.
Original comment by bitter...@gmail.com
on 15 May 2011 at 11:49
Original comment by 5h3l...@gmail.com
on 21 May 2011 at 1:49
I still cannot reproduce this issue however, any more details? Can you try to
open the terminal and paste the output here?
Original comment by 5h3l...@gmail.com
on 11 Jun 2011 at 2:47
Issue 323 has been merged into this issue.
Original comment by 5h3l...@gmail.com
on 11 Jun 2011 at 3:00
Apparently this issue has been already solved. I tried myself with
non-important DM contents, and it worked flawlessly. As far as I have
upgraded my OS and reinstalled hotot, I've got to check if this issue is
still happening or if it's definitely history.
Original comment by mando...@gmail.com
on 14 Jun 2011 at 7:50
This issue was closed by revision 0dcf32d3ea5b.
Original comment by 5h3l...@gmail.com
on 17 Jun 2011 at 2:46
Original issue reported on code.google.com by
amithsv...@gmail.com
on 4 Apr 2011 at 9:06