1044188 - Standalone -- change unsupported browser notice to be more accurate

Status: RESOLVED FIXED

(Hello (Loop) :: Client, defect)

Description

[Maire Reavy [:mreavy]]

When a link-clicker clicks on a URL from a browser that doesn't suport WebRTC, he/she sees: "To use Loop, please use the latest version of Firefox."   Instead the link clicker should se "Please try this link in a WebRTC-enabled browser."

Comment 1

[Maire Reavy [:mreavy]]

Attachment: Update message for link clickers using browsers without WebRTC support

Comment 2

[Maire Reavy [:mreavy]]

Attachment: Update message for link clickers using browsers without WebRTC support

Comment 3

[Maire Reavy [:mreavy]]

Attachment: Update message for link clickers using browsers without WebRTC support

Comment 4

[Dan Mosedale (:dmosedale, :dmose)]

Comment on attachment 8462854 [details] [diff] [review]
Update message for link clickers using browsers without WebRTC support

Review of attachment 8462854 [details] [diff] [review]:
-----------------------------------------------------------------

Since there's not yet a process in place for anyone to translate our standalone strings, and this one's going to have to change before long anyway, I don't think it's a problem leave the string id as is. 

ux-r not currently required.

r=dmose

Comment 5

[Dan Mosedale (:dmosedale, :dmose)]

https://hg.mozilla.org/integration/mozilla-inbound/rev/ba25d50a0b8b

Comment 6

[Romain Testard [:RT]]

Is this bug only about a non supported browser on a supported platform?

If yes then we need a bug for non supported platforms (iOS) - we had https://bugzilla.mozilla.org/show_bug.cgi?id=974895 although it's now been closed - should we just re-open it to implement the new UX?

We need some UX here as it's not part of the current link clicker design.

Comment 7

[Carsten Book [:Tomcat]]

https://hg.mozilla.org/mozilla-central/rev/ba25d50a0b8b

Comment 8

[Mark Banner (:standard8)]

(In reply to Romain Testard [:RT] from comment #6)
> Is this bug only about a non supported browser on a supported platform?

The filed definition was unclear.

> If yes then we need a bug for non supported platforms (iOS) - we had
> https://bugzilla.mozilla.org/show_bug.cgi?id=974895 although it's now been
> closed - should we just re-open it to implement the new UX?

If the device isn't supported, then we currently show:

===
Sorry, Loop does not currently support your device.
Please open this page using the latest Firefox on Windows, Android, Mac or Linux.
===

If we want to change that as well, please file a new bugs. Re-opening old bugs generally doesn't work and messes up tracking if backports are needed.

Comment 9

[Romain Testard [:RT]]

Thanks. I created a new bug to track the implementation of a new UX for non supported platforms: https://bugzilla.mozilla.org/show_bug.cgi?id=1045495

We need a new UX for this bug (current NI to Darrin) and I also NI Arcadio who was interested in this scenario in past conversations around promotion of Firefox to non current Firefox users. Arcadio please let us know quickly if you require a particular wording there.

Comment 10

[Mark Banner (:standard8)]

(In reply to Romain Testard [:RT] from comment #9)
> We need a new UX for this bug (current NI to Darrin) and I also NI Arcadio
> who was interested in this scenario in past conversations around promotion
> of Firefox to non current Firefox users. Arcadio please let us know quickly
> if you require a particular wording there.

We've already landed the patch here, and Maire has requested that we push this text live asap. I don't know where it came from, but please can we handle further changes (which I assume will be non-urgent) in another bug.

Comment 11

[Romain Testard [:RT]]

OK - new bug created to track new UX implementation: https://bugzilla.mozilla.org/show_bug.cgi?id=1045498

Comment 12

[u279076]

I believe this bug should be covered well enough with smoketesting via https://moztrap.mozilla.org/manage/case/14509/. Please needinfo me to request specific testing.