Closed Bug 808211 Opened 13 years ago Closed 13 years ago

Facebook did not prompt me to enable Facebook Messenger for Firefox

Categories

(Firefox Graveyard :: SocialAPI: Providers, defect)

17 Branch
x86_64
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: fb+mozdev, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Firefox/17.0 Build ID: 20121023124120 Steps to reproduce: Visit facebook.com. Actual results: Nothing special. Expected results: Facebook should have promoted me to turn on its SocialAPI integration. At least this is what I heard and thus expected. I was able to install it manually via [1]. I just wanted to point this out. This might be related to addons (Adblock Plus?) – though I cannot cross-check this as I cannot remove the SocialAPI-App (or whatever it is called) in my build (this is fixed in another bug and probably in 17b4) and re-try with (some) addons disabled. However, this can just be a Facebook/server issue that I wasn't prompted (I'm on a Facebook server which always gets updated very late in a feature roll-out). [1] https://www.facebook.com/about/messenger-for-firefox
Component: Untriaged → SocialAPI: Providers
Hardware: x86 → x86_64
This bug is mostly just a heads-up. If this is Facebook-server related issue, this bug is probably WONTFIX.
For the moment, the promotion is only being sent to a small portion of users. That will increase gradually as we continue developing the feature. You can always activate manually from the landing page.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Ok, great. I was a bit confused by the media coverage, though, as many recommended just visiting facebook.com and then automatically being prompted.
Yeah, there was some confusion about that initially. We fixed our blog post and had some of the bigger stories corrected, but not before many people got the wrong information.
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.