- When you click the like/send button as of September 2011, an iframe pops up
- The iframe is cut off if the like button is at the edge of a container with the “overflow: hidden” property. This prevents use of “overflow: hidden” for clear-fixing.
- The iframe is always opened to the bottom right, so it causes a horizontal scrollbar or extends the page length if it’s placed towards the bottom right of the page.
- The comments Social Plugin offers no way to control number of replies to posts, so the plugin height is always variable – the site has to be designed around it.
- The Login Button Social Plugin doesn’t offer a logout or switch user option after logging in.
- The Facebook messaging system should be used to alert dev accounts of updates to the API.
- The documentation for the SDKs needs more real world examples.
- Use of FB.XFBML.parse() should accompany the Social Plugin documentation for cases where new plugins need to be initialized dynamically.
- An FB message should be posted to admin accounts of pages that currently use “FB.Canvas.setAutoResize” (and need to update to FB.Canvas.setAutoGrow ).
- The Social Plugin embed code should dynamically create <div id=”#fb-root” />, or mention it in the documentation another way, otherwise common users will have invalid code when including multiple plugins since multiple divs with the “fb-root” id will exist.
- The backend/curl-based API should be better documented since it is not PHP exclusive even though only a PHP SDK is provided. It sucks to have to translate to another language. Maybe supported translations of the SDK should be linked to in the docs, such as the coldfusion one http://facebooksdk.riaforge.org/ and the C# one (only mentioned in the blog, not in the docs! https://developers.facebook.com/blog/post/395 ).