Closed GoogleCodeExporter closed 9 years ago
Update from original reporter:
Because I hadn't checked, I quit Safari, changed it to 32-bit mode, and
restarted. Frankate worked. To confirm the reported behavior, I changed back
to 64-bit mode, and Frankate still worked! I then re-enabled my other
extensions one by one, quitting Safari between each and trying Frankate, which
continued to work.
I am now back to exactly the same configuration I started with, with multiple
windows and various web sites, and no restarts of any other apps or the OS, and
Frankate now works just fine.
Safari, and OS X, have been restarted a number of times since the update and
the reported behavior was consistent, so I'm thinking that somehow (and as a
software professional I can't imagine why) the 64-32-64 bit cycle unwedged some
piece of persistent state somewhere that had been blocking some facet of
Frankate's operation.
So, my problem is solved, but it may be worthwhile to keep this odd phenomenon
in mind if it comes up again.
Original comment by tedburgh...@gmail.com
on 13 Nov 2010 at 2:02
Thank you for report and quick comment it is working now :)
I can only point out Safari's extension support/framework is still immature and
sometimes you can see weird glitches which go away with time (or after Safari
restart or after extension re-install)
Original comment by ysol...@gmail.com
on 13 Nov 2010 at 3:07
Original issue reported on code.google.com by
tedburgh...@gmail.com
on 13 Nov 2010 at 1:32