Closed Bug 751064 Opened 8 years ago Closed 8 years ago
Facebook like buttons and Google +1 buttons do not operate properly within apps not on facebook or google plus
Facebook like buttons and google +1 buttons do not work correctly in the desktop web runtime. Typically in a browser, connections are made to facebook account management and google account management to link the account, but clicking the link for the like or +1 button would then change the like or +1 button on the actual page. In an app, this does not work correctly. With facebook, the default browser starts up. Logging in sends me to a page of nothingness. With google plus, the default browser starts up, I enter my account information, hit confirm and +1, but nothing happens. Example scenario: 1. Install Sandglaz (https://marketplace-dev.allizom.org/en-US/app/sandglaz-1/) 2. Launch that application 3. Click the facebook like button on the bottom of the application Expected: A application pop-up should appear for www.facebook.com login. Logging in then result in changing the like button to the liked status. Actual: The default browser starts. Logging in will result in going to page of nothingness, probably cause it's trying to redirect back to the application. The facebook like button does not change to show the liked status.
Summary: Facebook like buttons and Google +1 buttons do not operate properly within the desktop web runtime → Facebook like buttons and Google +1 buttons do not operate properly within apps not on facebook or google plus
Nominating for k9o, as social integration is a key part of web apps (e.g. facebook, google plus).
blocking-kilimanjaro: --- → ?
Component: Desktop Runtime → Webapp Runtime
Product: Web Apps → Firefox
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
What fixed this? bug 752666?
(In reply to :Gavin Sharp (use email@example.com for email) from comment #2) > What fixed this? bug 752666? Yes.
Status: RESOLVED → VERIFIED
Whiteboard: [qa+] → [qa!]
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.