From Facebook Developers Wiki

fb:multi-friend-selector does exist now.

[edit] Cleanup

I hope I'm not stepping out of my bounds in doing a little cleanup of items that have been taken care of or are outdated. I'm moving the applicable issues to this page.

[edit] Not bugs/glaring omission

• The Profile Relationship Status is missing a Domestic Partners/Civil Union option. Are those with Domestic Partnerships and Civil Unions not welcome in Facebook?
  • This is a feature request for Facebook, not a bug or omission of the Facebook Platform
• We would like: users.getAppUsers to give us a list of all the uids of the users of the app.
  • This is a feature request, not a bug or omission.

• Developers should be allowed to set the privacy settings for thier own application, so that those who add the app can only see what the privacy settings will be, because it is pointless to add an app if you don't let it do what its supposed to do. Bascailly, instead of showing a bunch of checkboxes, it should show grayed out boxes for items that the developer has frozen, because they are necessary for the app to function.
  • Not a glaring omission

• Conditional comments get removed, leaving no easy way to create CSS for different browsers

• fb:user-table does not produce markup in the canvas page but does in the FBML console.

(JSeligstein): On the official documentation, this is listed as profile only. I think this will be changed eventually, but this is not a bug as of current.

• Mock Ajax clickrewriteurl fails if you use a apps.facebook* url. (It returns nothing and the indicated div becomes empty and unloved.)

Of course it does! You would be trying to load an entire facebook page which most certainly contains non-FBML code in it.

[edit] Fixed

• feed.publishStoryToUser docs don't detail the maximum size of the body attribute (there is one)
  • They do now

• editapp.php is still not working. Attempting to add a logo throws the error "You must provide a logo", and attmepting to add a description throws "You must provide an application description."
  • This has been long fixed

• When "only allow developers to add this application" is checked, the people listed as developers on the application's about page still can not add the application to their profile. (this has been fixed?)
  • Pretty sure this is fixed

• Table Picture Bug, where a user clicks on an application to update a picture and gets something from Ikea:

(JSeligstein): Known issue. I believe this has been fixed. Can you can refreshImageUrl on that image and verify if it is fixed?

(Barce): This is fixed. Thanks!

[edit] Outdated

• feed.publishActionOfUser is miscalculating feed points. I have only just turned it on and tried to set my own action (as the developer of the app in question) about 5 times. Now it fails every time. By my calculation, as I didn't use it at all yesterday, I should have 10 points. Each priority is worth 1/20th of a point. I'm sending these through with no priority so they have the default '1'. That means today I should have the ability to set 200 actions! New users, who have NEVER had anything set are also getting the error, so I assume it's calculating that I've hit the app-cap. There is, of course, no way that this could have happened either.
  • freshfunk5 pointed out in IRC that the calculation is being broken by the use of the ceiling() function. priority 1 and priority 20 both use a full feed point. And so anyone with 5 friends will use their entire feed point allocation on one message. The above scenario means that the 10 available points are absorbed by a single post to a user with 10 friends, or two posts to someone with 5. (editorial: Facebook is supposed to be about encouraging networking. Seems strange that friends matters in the calculation at all)
    • instead of being calculated as (#FeedPoints = ceil(pri / 20)) it would seem more appropriate to be (#FeedPoints = ceil(pri / 20) * num_recipients )
  • Feed points are no longer used

[edit] Other

• When you have code like
  and the corresponding CSS <style>#identifier{...}</style> the identifier in the div is rewritten to #${app_id}identifier but the CSS identifier is left unchanged (and unmatching)

  • Duplicate
• The following are duplicates of an already-posted bug:
  • MSIE-style opacity is being stripped out of inline styles. e.g. "filter: alpha(opacity=40);" is being removed from style="" attributes.
  • CSS issue for ie - filters - equal sign causes error by fbml parser

 p{
    opacity:0.5;
    filter: alpha(opacity=50); /* ie hack causes facebook to complain and results in page rendering failure*/
 }