The launch of Firefox Hello will have an associated tour, which will require some additions to our UITour to allow interaction with Hello. This bug tracks that work.

A few other parts that will be implemented by other bugs which are probably already filed elsewhere: * Hello button should glow blue until tour is started or skipped * Hello panel gear button should have a "Tour" entry to take tour again (verified strings already landing for 35) * Hello's First Time Experience (FTE) flavor of the panel with a Get Started button that launches the tour. I think we'll also want some way to skip the tour without launching it. Maybe overload the close button on the TOS/privacy section of the panel to skip the tour as well?

First Time Experience panel via https://people.mozilla.org/~dhenein/loop/rooms/

Updated wireframes

Is there a demo version that can be tested of this tour?

I don't think work has started on the webpage yet and I'm just starting on bug 1080944 today.

What Matt said. Implementation hasn't even started yet, far too early to be talking about testing it.

Hey Matt -- Which of the UI Tour bugs do we want to uplift to Fx35? Can you and/or Dolske write uplift approvals for the bugs that need to be uplifted --- and then needinfo me on the bugs that should be uplifted? (I'll then make sure they actually get uplifted.) I'm doing the needinfo to you from the meta bug because I thought that was cleaner/simpler than doing it on each of the individual bugs. Thanks!

(In reply to Maire Reavy [:mreavy] (Plz needinfo me) from comment #8) > Hey Matt -- Which of the UI Tour bugs do we want to uplift to Fx35? Can you > and/or Dolske write uplift approvals for the bugs that need to be uplifted > --- and then needinfo me on the bugs that should be uplifted? (I'll then > make sure they actually get uplifted.) The bugs have approvals but I will uplift them tomorrow to make sure they're done in the right order without bitrotting each-other unless someone else wants to take the time. It's probably worth doing a try build since there could be dependencies that aren't obvious.

Thanks, Matt -- If you do decide to do the uplifts, can you coordinate with me and Jesup? (To make sure we don't conflict with one another since we have a few patches we're looking to uplift.) Alternatively, Jesup and I could do all the uplifts (including the UI Tour) as long as you write the approval requests for UI Tour bugs and let us know what we should test. FYI: We test & verify everything we uplift with try builds before we push.

(In reply to Maire Reavy [:mreavy] (Plz needinfo me) from comment #10) > Thanks, Matt -- If you do decide to do the uplifts, can you coordinate with > me and Jesup? (To make sure we don't conflict with one another since we have > a few patches we're looking to uplift.) Alternatively, Jesup and I could do > all the uplifts (including the UI Tour) as long as you write the approval > requests for UI Tour bugs and let us know what we should test. FYI: We test > & verify everything we uplift with try builds before we push. You're welcome to do it if you want to take the time to do them in order to avoid rebasing. The bugs already have approval AFAIK so I think they can just land after testing on Try.

Should this be resolved fixed? It looks like all of the dependent issues are resolved.

Agreed. The project this was tracking is basically done.

Verified