Google Chrome Projects Bug January 27, 2010 4:17 PM Subscribe
Small alignment bug in Projects with Google Chrome.
This seems to be a Google Chrome bug, as it doesn't happen in Firefox (and I haven't checked any others). When the Projects link is clicked on, or navigated to via another way, the Votes boxes are not aligned quite right. If you resize the window, it fixes itself. If you refresh the page, or if you navigate away and come back, the alignment is off again.
It's a small thing, but my symmetry OCD requires that I speak up.
This seems to be a Google Chrome bug, as it doesn't happen in Firefox (and I haven't checked any others). When the Projects link is clicked on, or navigated to via another way, the Votes boxes are not aligned quite right. If you resize the window, it fixes itself. If you refresh the page, or if you navigate away and come back, the alignment is off again.
It's a small thing, but my symmetry OCD requires that I speak up.
Oh funny, thi smust be some sort of font-size related thing because it's only happening on the really short projects. I'm sure pb can fix it before I even finish typing this sentence.
posted by jessamyn (staff) at 4:21 PM on January 27, 2010
posted by jessamyn (staff) at 4:21 PM on January 27, 2010
Thanks for letting us know, it was off in Safari too. The votes boxes should be lining up now.
posted by pb (staff) at 4:39 PM on January 27, 2010
posted by pb (staff) at 4:39 PM on January 27, 2010
Also Chrome related: I can't flag anything in Chrome 4.0.302.2 dev on ubuntu. When I click [!], the "pick a reason to flag" box opens up, but when I click on the box it collapses back into the [!].
posted by stavrogin at 4:39 PM on January 27, 2010
posted by stavrogin at 4:39 PM on January 27, 2010
ditto as stavrogin, running Chromium (4.0.279.0) on Windows 7 and I can't flag.
posted by litleozy at 4:49 PM on January 27, 2010
posted by litleozy at 4:49 PM on January 27, 2010
sorry stavrogin, we can't support the bleeding edge versions of Chrome. Flagging is working fine for me on Ubuntu running the latest stable release, Chrome 4.0.249.43. With early releases like that it's tough to know if it's Chrome that has the problem or us.
I don't have a copy of Windows 7 handy to test, litleozy. Is that a developer version?
posted by pb (staff) at 4:53 PM on January 27, 2010
I don't have a copy of Windows 7 handy to test, litleozy. Is that a developer version?
posted by pb (staff) at 4:53 PM on January 27, 2010
Same as stavrogin, Chrome 4.0.266.0 on Windows 7.
posted by shakespeherian at 4:53 PM on January 27, 2010
posted by shakespeherian at 4:53 PM on January 27, 2010
Also, FWIW, flagging in Chrome works fine on my work computer, which is XP (not sure on the Chrome version, but I believe it's the beta channel so probably 4.0.266.0).
posted by shakespeherian at 4:55 PM on January 27, 2010
posted by shakespeherian at 4:55 PM on January 27, 2010
Yeah, I'm guessing right now the flagging thing is a problem with an early version of Chrome that will be fixed up when it's released.
posted by pb (staff) at 4:57 PM on January 27, 2010
posted by pb (staff) at 4:57 PM on January 27, 2010
I have the same problem with flagging -- Windows 7 x64, Chrome 4.0.302.3 dev.
You can work around it by clicking the [!], navigating through the list with the up/down arrows, and clicking somewhere else on the page to trigger the request.
posted by teraflop at 10:12 PM on January 27, 2010 [1 favorite]
You can work around it by clicking the [!], navigating through the list with the up/down arrows, and clicking somewhere else on the page to trigger the request.
posted by teraflop at 10:12 PM on January 27, 2010 [1 favorite]
Cool, thanks pb.
I can flag fine on Windows 7. Chrome version 4.0.249.78.
posted by SpacemanStix at 10:15 PM on January 27, 2010
I can flag fine on Windows 7. Chrome version 4.0.249.78.
posted by SpacemanStix at 10:15 PM on January 27, 2010
ah, thanks, teraflop. You just got flagged for a fantastic comment.
posted by stavrogin at 10:24 PM on January 27, 2010
posted by stavrogin at 10:24 PM on January 27, 2010
I wouldn't worry, it's all been fixed in Chrome 5.0
posted by blue_beetle at 12:31 PM on January 28, 2010
posted by blue_beetle at 12:31 PM on January 28, 2010
You are not logged in, either login or create an account to post comments
posted by Kattullus at 4:20 PM on January 27, 2010