SUMO community discussions

Firefox 124 for Mobile - Contributor thread

  1. Important note: If you're a user looking for product support, please post in the support forum instead.

    ---

    Hey everybody,

    Firefox 124 was released yesterday. And as usual, we're going to use this thread to collect feedback and trending issues related to Firefox mobile version 124.

    To find out more information about this release, please check out the following links:

    For existing issues/known feedback, as usual, please check out the following Trello boards:

    Thanks, everybody!

    '''Important note: If you're a user looking for product support, [https://support.mozilla.org/questions/new please post in the support forum instead.]''' --- Hey everybody, Firefox 124 was released yesterday. And as usual, we're going to use this thread to collect feedback and trending issues related to Firefox mobile version 124. To find out more information about this release, please check out the following links: * [https://wiki.mozilla.org/Support/Firefox124 Firefox 124 SUMO Sprint page] * [https://community.mozilla.org/en/events/firefox-124-sumo-sprint/ Community Event page] * [https://mozilla.hosted.panopto.com/Panopto/Pages/Sessions/List.aspx#folderID=%2230642208-b3d1-4543-93b9-ae31010f0aef%22 Support release Scrum Meetings] For existing issues/known feedback, as usual, please check out the following Trello boards: * [https://trello.com/b/ZVPjwv2t/mobile-feedback-board Mobile feedback board] * [https://trello.com/b/hgMGAugH/mobile-bug-board Mobile bug board] Thanks, everybody!
  2. Hey folks,

    I want to direct your attention to this issue on iOS that we have seen spiking pretty recently. The product team has acknowledged this issue and consider this as part of the bigger problem with external links on iOS. The team is working on a fix for this and looking into if we can ship it as part of the mobile dot release next week. There's a whole set of effort to fix the whole external links issues from the iOS team so some fixes may follow in the next releases or so.

    Please reach out here if you have see other trending issue on mobile after we launched version 124.

    Hey folks, I want to direct your attention to [https://github.com/mozilla-mobile/firefox-ios/issues/19262 this issue] on iOS that we have seen spiking pretty recently. The product team has acknowledged this issue and consider this as part of the bigger problem with external links on iOS. The team is working on a fix for this and looking into if we can ship it as part of the mobile dot release next week. There's a whole set of effort to fix the whole external links issues from the iOS team so some fixes may follow in the next releases or so. Please reach out here if you have see other trending issue on mobile after we launched version 124.
  3. Hey team! Following up on the above note from Kiki, the Product team has actually distinguished 2 distinct (but related) iOS issues regarding about:blank. If you see reports in the forum, we have these 2 open GitHub tickets to follow:

    • Clicking links that open a new tab instead open about:blank (GH 19262 GH 19262): Investigation in progress
    • Opening a link in external app leaves a "loading" about:blank page behind (GH 17571 GH 17571): Fix should land next week
    Hey team! Following up on the above note from Kiki, the Product team has actually distinguished 2 distinct (but related) iOS issues regarding about:blank. If you see reports in the forum, we have these 2 open GitHub tickets to follow: * Clicking links that open a new tab instead open about:blank ([https://github.com/mozilla-mobile/firefox-ios/issues/19262 GH 19262] GH 19262): Investigation in progress * Opening a link in external app leaves a "loading" about:blank page behind ([https://github.com/mozilla-mobile/firefox-ios/issues/17571 GH 17571] GH 17571): Fix should land next week
  4. Another emerging issue in iOS: Night mode switch is missing in version 124 (GH 19365).

    Another emerging issue in iOS: Night mode switch is missing in version 124 ([https://github.com/mozilla-mobile/firefox-ios/issues/19365 GH 19365]). * https://support.mozilla.org/en-US/questions/1443105 (16 votes) * https://support.mozilla.org/en-US/questions/1443158 (2 votes)
  5. Hi team -- following up on the above. An iOS eng followed up to let us know that Night mode (which makes the app chrome dark themed and inverts website content) is currently in an experiment to be removed. Starting back on March 15, 50% of all customers no longer see the Night mode switch in the hamburger menu. They are using the experiment to monitor the impact of removing, before they decide whether to remove entirely. Please flag if you start to notice more trends of feedback around this on the forum -- thanks!

    Hi team -- following up on the above. An iOS eng followed up to let us know that Night mode (which makes the app chrome dark themed and inverts website content) is currently in an experiment to be removed. Starting back on March 15, 50% of all customers no longer see the Night mode switch in the hamburger menu. They are using the experiment to monitor the impact of removing, before they decide whether to remove entirely. Please flag if you start to notice more trends of feedback around this on the forum -- thanks!
  6. Hello wonderful contributors! I have yet another update regarding Night Mode. The Product Team took our users' feedback to heart regarding their complaints about missing Night Mode. The experiment has ended, and Night Mode should be available again to all users by end of day. Thanks everyone!

    Hello wonderful contributors! I have yet another update regarding Night Mode. The Product Team took our users' feedback to heart regarding their complaints about missing Night Mode. The experiment has ended, and Night Mode should be available again to all users by end of day. Thanks everyone!
  7. Thank you Mandy for the detailed results about this! I always wonder how some of those experiments from about:studies end.

    My curiosity has been peaked: Can I ask why the Night Mode feature was even up for removal?

    Was the thinking behind that: If user adoption of Night Mode is low, we should remove it? It seems like a useful feature & more users are admitting they don't like to be hit by blinding white pages, especially at night. Maybe all product teams are tasked with removing features or UX elements that's considered redundant or very rarely used. But I'm curious to hear from their perspective how this experiment came about. I wonder if more of the reasoning on why they wanted to remove it is listed in the experiment's description area, if you have access to that.

    Sometimes it's brief & doesn't explain the why. But other times, it does: Example detailed experiment description: experimentType": "rollout", "source": "rs-loader", "userFacingName": "Add an Image to PDF (with Alt Text) - Rollout", "userFacingDescription": "One of the important features users need when managing their PDF files is adding an image. Users want an easy way to add an image to their PDF documents that they can easily resize and move around the document. This experiment measures the impact of launching this feature for Firefox users and if that impacts their usage in any way. Specifically, we are trying to understand the impact on Firefox Daily Active Users (DAU) as a result of launching this feature."

    Sorry if I'm overthinking this. It just feels weird to me that this feature came up on the chopping block. So naturally I start to question why. :)

    Thank you Mandy for the detailed results about this! I always wonder how some of those experiments from about:studies end. My curiosity has been peaked: Can I ask why the Night Mode feature was even up for removal? Was the thinking behind that: If user adoption of Night Mode is low, we should remove it? It seems like a useful feature & more users are admitting they don't like to be hit by blinding white pages, especially at night. Maybe all product teams are tasked with removing features or UX elements that's considered redundant or very rarely used. But I'm curious to hear from their perspective how this experiment came about. I wonder if more of the reasoning on why they wanted to remove it is listed in the experiment's description area, if you have access to that. Sometimes it's brief & doesn't explain the why. But other times, it does: Example detailed experiment description: experimentType": "rollout", "source": "rs-loader", "userFacingName": "Add an Image to PDF (with Alt Text) - Rollout", "userFacingDescription": "One of the important features users need when managing their PDF files is adding an image. Users want an easy way to add an image to their PDF documents that they can easily resize and move around the document. This experiment measures the impact of launching this feature for Firefox users and if that impacts their usage in any way. Specifically, we are trying to understand the impact on Firefox Daily Active Users (DAU) as a result of launching this feature." Sorry if I'm overthinking this. It just feels weird to me that this feature came up on the chopping block. So naturally I start to question why. :)
  8. Hi Noah! Happy to share my understanding of the Night Mode experiment based on my conversations with Product. Night Mode had low adoption rates by customers -- the experiment was exploring the impact of removing Night Mode in order to improve app stability. Having said that, it became clear during the experiment that although adoption is low, this is a necessary accessibility feature for those who rely on it. In short, the experiment did its job by showcasing just how indispensable this feature is for that subset of users.

    Experiments in general can have many purposes (and I hope to communicate those to the Contributor community moving forward when they have been shared with me). In general, reasons for experiments are often geared towards feature adoption, funnel improvements, and app performance improvements. Hope this helps!

    Hi Noah! Happy to share my understanding of the Night Mode experiment based on my conversations with Product. Night Mode had low adoption rates by customers -- the experiment was exploring the impact of removing Night Mode in order to improve app stability. Having said that, it became clear during the experiment that although adoption is low, this is a necessary accessibility feature for those who rely on it. In short, the experiment did its job by showcasing just how indispensable this feature is for that subset of users. Experiments in general can have many purposes (and I hope to communicate those to the Contributor community moving forward when they have been shared with me). In general, reasons for experiments are often geared towards feature adoption, funnel improvements, and app performance improvements. Hope this helps!
  9. more options

    Spammer copied a reply above then posted a spam link under it

    
      
    ''Spammer copied a reply above then posted a spam link under it'' <!-- Just a heads up, we've noticed a surge in an iOS issue lately, particularly with external links. Our product team is fully aware and is treating it as a component of the broader problem. We're actively working on a solution and exploring the possibility of including it in the upcoming mobile dot release next week. Rest assured, the iOS team is committed to addressing all aspects of the external links issue, so expect further fixes in subsequent releases. If you spot any other emerging mobile issues post-version 124, please don't hesitate to flag them here. --> <!--Visit my Website https://recipedoor.com/-->

    Modified by NoahSUMO on

  10. Thanks Mandy for getting me an answer on this! That helps confirm what I was thinking. It also sounds like Night Mode wasn't as perfect as I thought. I did read a thread or two where it made sites that were already dark, a bit darker. But if there was more stability problems with it, that's surprising. I hope Night Mode keeps getting better.

    Sharing future experiments with us would definitely be appreciated since we could know right away that a addon wasn't breaking something. So thanks in advance.

    I think my biggest concern with experiments that confuse users is that they'll go into extreme troubleshooting & out of desperation, uninstall & reinstall Firefox on Android/iOS & potentially lose their data. So one day I'd love to see a way to backup the browser data locally to the phone to combat this.

    Thanks Mandy for getting me an answer on this! That helps confirm what I was thinking. It also sounds like Night Mode wasn't as perfect as I thought. I did read a thread or two where it made sites that were already dark, a bit darker. But if there was more stability problems with it, that's surprising. I hope Night Mode keeps getting better. Sharing future experiments with us would definitely be appreciated since we could know right away that a addon wasn't breaking something. So thanks in advance. I think my biggest concern with experiments that confuse users is that they'll go into extreme troubleshooting & out of desperation, uninstall & reinstall Firefox on Android/iOS & potentially lose their data. So one day I'd love to see a way to backup the browser data locally to the phone to combat this.
  11. Such a great point about user desperation leading to uninstall+reinstall and risk of losing data, Noah. Any issue contributing to loss of data yields high user churn, so I will flag this sentiment to the Product team! Thanks for your insights.

    Separately, I wanted to flag that you may have seen some recent reports of password autofill issues on iOS. This bug was also due to a recent experiment that has now ended. I believe this experiment was about improving abilities to select from options if you have multiple passwords saved. If users can update to V124.3, they should regain access to autofill passwords again. Thanks!

    Such a great point about user desperation leading to uninstall+reinstall and risk of losing data, Noah. Any issue contributing to loss of data yields high user churn, so I will flag this sentiment to the Product team! Thanks for your insights. Separately, I wanted to flag that you may have seen some recent reports of password autofill issues on iOS. This bug was also due to a recent experiment that has now ended. I believe this experiment was about improving abilities to select from options if you have multiple passwords saved. If users can update to V124.3, they should regain access to autofill passwords again. Thanks!