I know that IE7 is obsolete now, but there is a lot of people that still use it. And I also understand that probably this not a module problem, it's a FB problem, but in this way it should be alerted to the FB developers.
In node pages it keeps loading something (code probably) almost infinitely, in a way that if you goes page up or down it locks it, holds it. It takes almost 2 minutes to end up everything.
In the front page it is the worst, since you may have 5, 10, 20 widgets doing the same thing. In this way, browsing from front page is almost impossible.
I had seen in the developers pages and forums that there is two ways to display the button, I don't know if the module is using the obsolete one, if it is you should think to upgrade it as soon as possible...
Thanks for attention.
Comments
Comment #1
mrfelton commentedsubscribe
Comment #2
ferdi commentedThe module is using the "new way" (latest javascript SDK http://developers.facebook.com/docs/reference/javascript/) and as you point out there is not much we can do. There is another way, using iframe instead of javascript but it has some limitations (http://developers.facebook.com/docs/reference/plugins/like)
We could offer an option to switch between javascript and iframe if that helps with the speed.
thanks!
Comment #3
Vuds commentedIt has some time since I had written the issue. In the meantime, I had disallowed the module, and had returned to use the button last week, but using the code Facebook offers (not the module) embed in a block. And found that It still suffers from what I described.
Now that there is 6 months since opened this issue, more people wrote about this, and it's really a Facebook fault: from what I read, this "simple" button calls for 13 to 17 different servers (!) before it shows. Some browsers are very sensitive on this, locking navigation while the page doesn't loads completely (IE7 is the best example of this).
Solution for now? While Facebook doesn't hear from developers' appeal all over the world blaming about this, I just enabled the button to work only inside a content node view, and pray that people start using more FF or Chrome, or even IE8. It's still unacceptable to use with links area for front page.
As for the module, my tests had demonstrated that it doesn't matter if you choose iframe or XFBML. Then it's your choice to enable it or not.
I have set this as postponed, since it's not module fault, and it will have to wait for a Facebook action.
Thanks for attention!
Comment #4
zoia commentedLine: 7
Char: 776
Code: 0
URI: http://static.ak.connect.facebook.com/js/api_lib/v0.4/FeatureLoader.js.p...
how can i get rid of this error
Comment #5
djbobbydrake commentedSubscribing.