Skip to content

Conversation

@jpetto
Copy link
Contributor

@jpetto jpetto commented Feb 11, 2016

Have not yet updated firefox/accounts.js as I wanted to first get a sanity check on the approach.

Code is up on demo5:

https://www-demo5.allizom.org/en-US/firefox/46.0/firstrun/

Change isn't immediately obvious, so I'm logging the FxA iframe src to the console. If Fx 46+, src string should contain context=fx_firstrun_v2. Otherwise, context=iframe.

Actual change - after verifying email, Fx 46+ users see a blue "Sync Preferences" button in the iframe. Fx < 46 users do not get this button.

@alexgibson - Pre-review on approach? What do you think about the UITour fallback and timing?


console.log('fx version = ' + version);

if (version >= 46) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I may well be missing something, but if you're only after the major version number then using UITour for this could be overkill perhaps? If you needed the minor version or channel name then UITour is the only way, but if the major version number is the only thing of importance, then I would probably use Mozilla.Client.FirefoxMajorVersion instead. This is both synchronous and does not require any special config.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I went right for the big guns, didn't I? Refactoring...

@jpetto jpetto force-pushed the bug-1243890-update-fxa-iframe-param-fx46 branch from ff9f3a2 to 55f5702 Compare February 12, 2016 16:03
@jpetto
Copy link
Contributor Author

jpetto commented Feb 12, 2016

Okay, I think I've stopped trying too hard. 😁

Ready for a real review.

@alexgibson
Copy link
Contributor

When I updated the bedrock docs for local testing, I totally forgot to include the bit about using the right port (127.0.0.1:8111) - could you add it back here? 😄

@jpetto
Copy link
Contributor Author

jpetto commented Feb 12, 2016

When I updated the bedrock docs for local testing, I totally forgot to include the bit about using the right port (127.0.0.1:8111) - could you add it back here? 😄

I think I can handle that. 👍

- Update FxA docs to include local server IP/port
@alexgibson
Copy link
Contributor

Tested locally and both pages are working as expected with the correct iframe query params, and I see blue button after verifying email in FF 46+ 👍

r+wc from me once the docs are updated for my faux pas

Also noted that we should probably look to consolidate this code for the iframe sometime in the future, as there's a fair bit of duplication now?

@jpetto jpetto force-pushed the bug-1243890-update-fxa-iframe-param-fx46 branch from 55f5702 to 644e2ff Compare February 12, 2016 16:33
alexgibson added a commit that referenced this pull request Feb 12, 2016
…aram-fx46

[fix bug 1243890] Update FxA iframe param for Fx46.
@alexgibson alexgibson merged commit 17dfdd9 into master Feb 12, 2016
@alexgibson alexgibson deleted the bug-1243890-update-fxa-iframe-param-fx46 branch February 12, 2016 16:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants