Bug 632749 – Doesn't show bookmark manager or code source (if dual-monitor) -
Firefox 4.1, OS X 10.6.7:
15” MacBook Pro with 24” Apple LED Cinema Display. ACD is primary display (has menubar). MBP is to left of ACD.
1) Place FF window on MBP screen.
2) Go to http://google.com/
3) Hit CMD+U
4) Nothing appears, though “Source of: http://google.com/” does appear as last item in Window menu.
Placing window 50% or more on ACD screen works as expected. Changing arrangement of displays so that MBP is to right of ACD also works as expected on both displays.
All it would take for me to abandon Firefox forever is for someone to fork a version that strips out all the junk and bakes in Firebug (which is still way better than WebKit’s inspector).
I’m not sure what’s worse, the bug itself, or the “WFM” refrains from the developers.
[video]
“On March 23, 2011, Justin Vernon told Rolling Stone that a follow up of For Emma, Forever Ago would be released in June. The untitled album will be composed of 10 songs and take a new musical direction.” — Bon Iver - Wikipedia, the free encyclopedia
[video]
I agree with this 110%. These are my exact sentiments. The troubling thing is that there is obviously something TinyGrab is not telling us.
The guys over at TinyGrab are running a clinic on how not to handle a crisis.
A few weeks ago, TinyGrab’s servers were apparently hacked, and because of that they released new, untested software that completely doesn’t work. This makes no sense. They claim that due to someone accessing and “corrupting the kernel” (really?) of their servers, they had to completely abandon TinyGrab 1.0’s server-side codebase, as well as completely invalidate the client applications immediately.
I’m not sure I understand why this was necessary at all. If your server gets hacked you undo the damage, repair the codebase from your repository, increase/modify security, patch any holes, and you’re back to the races. If your client application needs modifications because of changes to security on the server-side, issue an update through regular channels. This could be done and solved in relatively quick time, depending on how much code needed to be updated. You can even force users to reset their passwords if necessary.
Instead, TinyGrab threw a perfectly functional client app away entirely, they removed all of their 1.0 code on the server, and they released new 2.0 versions of their client applications which aren’t at all production ready. The Mac version of the app doesn’t support even half of the functionality of the 1.0 app, and the website is a complete shambles. Most people cannot log in (including myself), and it’s total garbage.
Here’s the ridiculous thing: I paid for the TinyGrab “premium” features (a one-time unlock fee) so that I could use FTP support and have my screenshots uploaded to my own server. Guess what feature is completely missing from TinyGrab 2.0? That’s right—FTP uploads. So when TinyGrab switched over to this new, shitty client app, they completely removed the only feature I use. Well, that’s helpful!
Taken with Instagram at Carlsbad Village Station
Swingin’ (Taken with instagram)
[video]
NERDS (Taken with instagram)