Patrick,
With the 4.3 release, we introduced a CSS bug that will be fixed in the v4.3.1 version, coming out later this week. To fix now, edit the /components/com_jfbconnect/assets/jfbconnect.css file and remove the following CSS tags:
#fbcomments, .fb_iframe_widget, .fb_iframe_widget[style], .fb_iframe_widget iframe[style], #fbcomments iframe[style], .fb_iframe_widget span {
width: 100% !important;
}That may fix the comments and like button issue, but may not. Either way, it will fix some other issues you may not even be aware of.
For the Like/Comments, the one thing that Facebook has big difficulties with is sites that use both www and non-www for URLs. I'd highly recommend setting up a redirect in your .htaccess file (or in a number of other possible places) to force your site to always, or never, use www. That's good for Facebook as well as search engines because when you have both, each variation of the URL looks like a completely separate page. Because of that, sometimes Facebook will 'group' the Likes and Comments together, other times the Like click will be for either the www or the non-www version. Then, if you view the site in the 'other' variant, you may not be grouped with the previous user.
It can be confusing, but in general, forcing a redirect may be what will fix your problem. It may take a few days for Facebook to realize the new canonical (final) URL to use, but will hopefully rectify itself.
Hope that helps explain, but if you need anything else, just let us know!
Thanks,
Alex