Beijing office used to show PopupNotifications anchored at relevant toolbar buttons, explaining their functions to new users. With the introduction of new onboarding experience and switch to WebExtensions API, we'd like to be able to customize the onboarding tour in our distribution. The single most important message for us, is the terminology change of "Favorites" to "Bookmarks" if an user comes from IE or other Chinese browsers. This may also mean we need to get necessary permission for our own home/newtab pages. They're currently served through http.

Hi Hector, could you provide more detail for the request? Or you can contact Cindy(PM) directly for help to better understand the need.

(In reply to Fred Lin [:gasolin] (OOO till 7/27) from comment #1) > Hi Hector, could you provide more detail for the request? > > Or you can contact Cindy(PM) directly for help to better understand the need. I'll join the regular Vidyo call between PEK & TPE teams tomorrow.

hi Peter, Cindy, would you please take a look of this suggestion?

As Hector mentioned, the plan is to understand the ask over Vidyo tomorrow afternoon.

Sorry, about not getting to this right after the meeting. So the behavior of the onboarding dialog can be controlled mostly by prefs. The details can be found here: http://searchfox.org/mozilla-central/source/browser/extensions/onboarding/README.md To add new tours we would need to get them check-in into central. It's should not be a problem IMHO since user will not see them unless you set the pref to show them. Let us know if this will work, if not, we can talk and figure out other solutions. I have a question, though: since you replace both the home and new tab page with your own, do you really need an onboarding overlay? Couldn't you just do that on your pages?

(In reply to Tim Guan-tin Chien [:timdream] (please needinfo) from comment #5) > > Let us know if this will work, if not, we can talk and figure out other > solutions. In my preliminary test, I can activate the current onboarding tour on our newtab page, but not our homepage. Our homepage "about:cehome" is a xul page which has a browser in it, where the real webpage is displayed, I'll see what I can do with it; We have some very generic selector on our newtab page, I can make them more specific to avoid conflict with the injected onboarding elements; Our newtab page needs to be granted uitour permission, and served through https for uitour permission to work. > > I have a question, though: since you replace both the home and new tab page > with your own, do you really need an onboarding overlay? Couldn't you just > do that on your pages? Essentially, we'd like the ability to highlight certain browser ui elements, and uitour permission should be good enough for that. But we'd also like to make applicable global messages available to users in China, and also avoid duplicated efforts. I hope this makes sense.

> In my preliminary test, I can activate the current onboarding tour on our > newtab page, but not our homepage. onboarding tour is filtered to show on about:home and about:newtab, so about:cehome will not shown the tour. > Our homepage "about:cehome" is a xul page which has a browser in it, where > the real webpage is displayed, I'll see what I can do with it; > We have some very generic selector on our newtab page, I can make them more > specific to avoid conflict with the injected onboarding elements; > Our newtab page needs to be granted uitour permission, and served through > https for uitour permission to work. > You can check bug 1357005 to know how to add permission for about:cehome, though web extension might not allow you to add about:cehome anymore, so it might not the right way. Instead, you can use the similar way how activity-stream to redirect about:newtab to their system addon, http://searchfox.org/mozilla-central/source/browser/components/newtab/aboutNewTabService.js with that approach you can still use URL `about:newtab` and `about:home` to serve `cehome` functionality. > > I have a question, though: since you replace both the home and new tab page > > with your own, do you really need an onboarding overlay? Couldn't you just > > do that on your pages? > > Essentially, we'd like the ability to highlight certain browser ui elements, > and uitour permission should be good enough for that. But we'd also like to > make applicable global messages available to users in China, and also avoid > duplicated efforts. I hope this makes sense. You'll got uitour permission when you use `about:newtab` and `about:home`, and onboarding tour will be there.

The onboarding tour discussed in this bug was removed in bug 1462415.