search

cezarsa / silver_bird

Extension to access your Twitter from the Google Chrome browser.
http://cezarsa.github.com/silver_bird/
MIT License
287 stars 87 forks source link

Tweet window too small and randomly positioned #410

Open peanutismint opened 10 years ago

peanutismint commented 10 years ago

This has only happened since I performed a clean install of Mac OS X Mavericks with the latest public build of Chrome (30.0.1599.101). When I click the SilverBird icon, the window that pops up is tiny, too small to do anything with, and positioned slightly away from its usual location.

screenshot 2013-11-08 03 20 57

Believe it or not, I can still actually navigate within that tiny window (scroll etc, not that I can see/read anything...!!) and if I click around a bit and navigate to a link to open one of my contacts twitter feeds in a separate SilverBird tab, for instance, the window opens up to its normal size.

Weird! :-)

BernhardValenti commented 10 years ago

I also get that every now and then... I also have most other extension getting cut off at the top (not always), so might be a Chrome issue? (fwiw, I had those issues since forever)

Grolubao commented 10 years ago

It is happening the same to me. It's very annoying, and I can hardly use Silver Bird after I upgraded to Mavericks

mountainash commented 10 years ago

+1 for this also occurring (and also being annoying).

peanutismint commented 10 years ago

Ok, so are we all thinking this is specifically a Mavericks issue then?

After living with this problem (Can't seem to find a better Twitter extension for Chrome...!!) for a while, I find I can get the window to fully open after a few clicks. Sometimes it takes 5 clicks, other times it takes more like 20...but it's seemingly at random.

Any ideas anybody?

BernhardValenti commented 10 years ago

Fixed in dev release I think. (IIRC I always had that issue on Mac, not only since Mavericks)

peanutismint commented 10 years ago

Hmm interesting... Is there a way for me (a lowly user) to install the dev release?

BernhardValenti commented 10 years ago

https://code.google.com/p/chromium/issues/detail?id=307912

"The fix has been merged to Chrome 33 (goes to stable around the beginning of March). We've requested a merge to Chrome 32 as well, which would allow us to get the fix out earlier, in mid-January."

BernhardValenti commented 10 years ago

http://www.chromium.org/getting-involved/dev-channel

peanutismint commented 10 years ago

Ah okay, thanks! :-)

mountainash commented 10 years ago

I've just upgraded to Chrome 32 and can confirm that this issue has not occurred again. Fixed!

peanutismint commented 10 years ago

Me too. Pretty happy! :+1: