Closed Bug 1043505 Opened 5 years ago Closed 5 years ago
White list about:home for Firefox Accounts landing page
We'd like to offer users an easy way to sign up from about:home. The feedback we’ve received is that about:home needs to be white listed in order to allow access to the Accounts sign up page. Experience would work as follows: - User opens Firefox and about:home loads - User sees a snippet with an accounts call to action and clicks link to create an account - User is directed to Firefox Accounts page and begins the sign up process
OS: Mac OS X → All
This depends on bug 1035586 - there's already a "showFirefoxAccounts" UITour command from bug 998934 that should allow this.
Assignee: nobody → jaws
Status: NEW → ASSIGNED
Iteration: --- → 34.1
Points: --- → 2
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Whiteboard: [fixed by bug 1035586]
Jared, per our conversation from IRC, I tried to verify the fix for this bug by adding a script element to the about:home page and calling Mozilla.UITour.showFirefoxAccounts() via dev tools, but I keep getting a reference error and the accounts snippet is not displayed. I also tried pretty much the same thing using Scratchpad, but again, with no success. Am I missing something? Or is there any other way QA can verify this?
QA Contact: cornel.ionce → andrei.vaida
We discussed this over IRC and Andrei got it figured out.
(In reply to Jared Wein [:jaws] (please needinfo? me) from comment #3) > We discussed this over IRC and Andrei got it figured out. Yeah, thanks again Jared for pointing me towards the right direction. This is now verified fixed on Nightly 34.0a1 (2014-07-31), by calling Mozilla.UITour.showFirefoxAccounts() directly from Web Console, which results in a redirection to about:accounts?action=signup. Platforms covered: Windows 7 64-bit, Mac OS X 10.9.4 and Ubuntu 13.04 32-bit.
Status: RESOLVED → VERIFIED
QA Whiteboard: [qa+] → [qa!]
Verified fixed on Aurora 33.0a2 (2014-08-04) and Firefox 32 Beta 4 (Build ID: 20140804164216) as well.
You need to log in before you can comment on or make changes to this bug.