1556520 - Automatically select AAQ for A) Fx Preview with UA >=69 B) Fennec with UA <= 68

Status: RESOLVED FIXED

(support.mozilla.org :: Questions, enhancement)

Description

[Seburo]

When the user agent is:

Mozilla/5.0 (Android x.y); Mobile; rv:a.a) Gecko/b.b Firefox/c.c

Where a.a is < 68, the AAQ should direct users to Firefox for Android.
Where a.a is >= 68, the AAQ should direct users to Firefox Preview.

Given that Firefox Preview is currently available to users to test, would appreciate a swift implementation.

Comment 1

[Roland Tanglao needinfo please :rolandtanglao, :mohnkuchen, :adobo, :sinigang, :roland]

The exact statement from https://github.com/mozilla-mobile/fenix/issues/1134#issuecomment-491412465 is:

• "In the meantime, the AMO and SUMO teams can proceed with their server-side UA checks for "Firefox Android version >= 69 means Fenix". That check will be valid even if we don't implement a UA override workaround for the overlapping period of Fennec/Fenix 68."

Comment 2

[Chris Peterson [:cpeterson]]

(In reply to Seburo from comment #0)

Mozilla/5.0 (Android x.y); Mobile; rv:a.a) Gecko/b.b Firefox/c.c

Where a.a is < 68, the AAQ should direct users to Firefox for Android.
Where a.a is >= 68, the AAQ should direct users to Firefox Preview.

Version 68 is ambiguous because Fennec and Fenix will both be version 68 for 2-6 weeks.

• Version >= 69.0 is unambiguously Fenix and not Fennec (because all Fennec users will be moved to the ESR 68 channel).
• Version < 68.0 is unambiguously Fennec and not Fenix.
• Version == 68.0 is ambiguous because Fennec and Fenix will have the same version!

During the overlap period, do we want to direct these version 68 users to SUMO's Fennec content or Fenix content? I assume SUMO will get more Fennec 68 visitors than Fenix 68 visitors, so directly them to Fennec content might make sense. OTOH, Fenix is the exciting new thing, so we might want to showcase the Fenix content.

Comment 3

[Seburo]

(In reply to Chris Peterson [:cpeterson] from comment #2)

During the overlap period, do we want to direct these version 68 users to SUMO's Fennec content or Fenix content? I assume SUMO will get more Fennec 68 visitors than Fenix 68 visitors, so directly them to Fennec content might make sense. OTOH, Fenix is the exciting new thing, so we might want to showcase the Fenix content.

Without mentioning any dates, how long is this overlap period?

(If under NDA, please email/Slack me)

Comment 4

[Chris Peterson [:cpeterson]]

(In reply to Seburo from comment #3)

(In reply to Chris Peterson [:cpeterson] from comment #2)

During the overlap period, do we want to direct these version 68 users to SUMO's Fennec content or Fenix content? I assume SUMO will get more Fennec 68 visitors than Fenix 68 visitors, so directly them to Fennec content might make sense. OTOH, Fenix is the exciting new thing, so we might want to showcase the Fenix content.

Without mentioning any dates, how long is this overlap period?

I don't know. Fenix MVP will ship with GV 68 Beta. We're using GV Beta builds because we're still iterating quickly. I'm just guessing that Fenix will probably update to GV 69 Beta in August instead of waiting for GV 69 Release (September 3).

jonalmeida said he still might be able to finish the UA spoofing (mozilla-mobile/fenix#1134) in time for Fenix MVP. But even if he doesn't make the deadline, SUMO will still want to check for version >= 69 to detect Fenix in the future. So there is no difference in the server-side UA check that SUMO will need. :)

Comment 5

[Jonathan Almeida [:jonalmeida]]

The Fenix UA spoofing is complete. :)

🎉

Comment 6

[Roland Tanglao needinfo please :rolandtanglao, :mohnkuchen, :adobo, :sinigang, :roland]

(In reply to Jonathan Almeida [:jonalmeida] from comment #5)

The Fenix UA spoofing is complete. :)

🎉

"applause emoji" thanks :jonalmeida!

So is this the desired behaviour for SUMO from an Android device then :jonalmeida?
a) in the SUMO Ask a Question flow i.e. "AAQ" when the User Agent i.e. UA says "<=Firefox 68 for Android" (i.e. when surfing to support.mozilla.org/questions/new from Fennec on Android), select the Fennec AAQ by default

b) in the AAQ when the UA says ">=Firefox 69 for Android" (i.e. when surfing to support.mozilla.org/questions/new from Firefox Preview on Android), select the Fenix AAQ by default

Comment 7

[Chris Peterson [:cpeterson]]

(In reply to Roland Tanglao needinfo please :rolandtanglao, :mohnkuchen, :adobo, :sinigang, :roland from comment #6)

So is this the desired behaviour for SUMO from an Android device then :jonalmeida?
a) in the SUMO Ask a Question flow i.e. "AAQ" when the User Agent i.e. UA says "<=Firefox 68 for Android" (i.e. when surfing to support.mozilla.org/questions/new from Fennec on Android), select the Fennec AAQ by default

Yes. Android Firefox with UA version <= 68 is a Fennec user, so SUMO should show the Fennec AAQ.

b) in the AAQ when the UA says ">=Firefox 69 for Android" (i.e. when surfing to support.mozilla.org/questions/new from Firefox Preview on Android), select the Fenix AAQ by default

Yes. Android Firefox with UA version >= 69 is a Fenix user, so SUMO should show the new Fenix AAQ.

Also, jonichan said on GitHub that SUMO is adding text to every article:

• If viewing a fennec article from fenix:

  This article is for the old Firefox for Android, but you seem to be on Firefox Preview, our newest fasted, Android browser. Please visit the Firefox Preview knowledge base instead.

• If viewing a Fenix article from Fennec

  You are using our older mobile browser, but this article is for Firefox Preview, our newest, fastest browser. Download Firefox Preview here or visit the old Firefox for Android knowledge base.

Comment 8

[Jonathan Almeida [:jonalmeida]]

Clearing since cpeterson has answered this.

Comment 9

[Tasos Katsoulas [:tasos]]

The patch has been applied to the staging instance.

Comment 10

[Roland Tanglao needinfo please :rolandtanglao, :mohnkuchen, :adobo, :sinigang, :roland]

I just tested this with the "special ua spoofing on support.allizom.org Firefox Preview build" from :jonalmedia (thanks again jonathan!):

• https://github.com/mozilla-mobile/fenix/issues/3558

Will set to Resolved after a) deploying to prod b) testing on prod

Comment 11

[Tasos Katsoulas [:tasos]]

This is live in production. I am closing this bug as resolved.