is - so sadly -, not an xHTML valid tag. So, please avoid it's use, and use instead of it. fblikebutton.module at line 272
  $output = '<iframe src="https://www.facebook.com/plugins/like.php?' . $src . '" scrolling="no" frameborder="0" style="border: none; overflow: hidden; width: ' . $width . 'px; height: ' . $height . 'px;' . $other_css . '" allowTransparency="true"></iframe>';
should be
  $output = '<object style="border: none; overflow: hidden; width: ' . $width . 'px; height: ' . $height . 'px;' . $other_css . '" data="https://www.facebook.com/plugins/like.php?' . $src . '" type="text/html"></object>';

Comments

tommychris’s picture

< Iframe > is - so sadly -, not an xHTML valid tag. So, please avoid it's use, and use < object > instead of it.

jerdiggity’s picture

Assigned: Unassigned » jerdiggity
Status: Active » Closed (won't fix)

As described on the project page, the whole point of this module is to replace the need for users having to visit Facebook in order to obtain the like button code (among a few other things). The code could also be implemented by doing a little theme customization instead, but not everyone is savvy and/or driven enough to make such theme customizations.

I totally understand what you're saying, but the iframe tag is a valid xHTML tag:

http://www.w3.org/TR/2002/REC-xhtml1-20020801/dtds.html#dtdentry_xhtml1-...

Granted, this only applies to xHTML Transitional, but that doesn't make it "not an xHTML valid tag" (not 100%, at least).

Anyway, I really do appreciate the feedback/suggestion but unless/until the code rendered at http://developers.facebook.com/docs/reference/plugins/like/ changes to that of an object, I'll probably leave it the way it is for now.

Maybe we can add the option to choose between object and iframe or something?

ajaysolutions’s picture

The reason this isn't implemented by Facebook yet, despite you being absolutely correct in saying they should be using the object element, is that it doesn't display correctly in anything below IE9. Found that out today much to my dismay, I've had to put the site I was building back to not being compliant because unfortunately we're still supporting IE7 and 8 - thank god we don't have to bother with IE6 anymore though eh? ;)