>What other Fenix, GV, or Gecko work is needed to listen for enrollment in those (yet to be named) experiments and then enable SHIP or Fission? AC/Fenix: AC side is pretty simple, should just be defining the experiment in [geckoview.fml.yaml](https://searchfox.org/mozilla-central/source/mobile/android/android-components/components/browser/engine-gecko/geckoview.fml.yaml). (At worst, the [Nimbus experiment delegate](https://searchfox.org/mozilla-central/source/mobile/android/android-components/components/browser/engine-gecko/src/main/java/mozilla/components/experiment/NimbusExperimentDelegate.kt) might need expanded, but I havn't seen something to suggest that yet.) GeckoView: Glad you shared this specific bug! Yes, this should be one of the steps and this bug should be the main part of the GeckoView work. I was wondering if I could just add to the GeckoRuntimeSetting because of this [comment](https://searchfox.org/mozilla-central/rev/396a6123691f7ab3ffb449dcbe95304af6f9df3c/mobile/android/geckoview/src/main/java/org/mozilla/geckoview/RuntimeSettings.java#275
Bug 1771965 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
>What other Fenix, GV, or Gecko work is needed to listen for enrollment in those (yet to be named) experiments and then enable SHIP or Fission? AC/Fenix: AC side is pretty simple, should just be defining the experiment in [geckoview.fml.yaml](https://searchfox.org/mozilla-central/source/mobile/android/android-components/components/browser/engine-gecko/geckoview.fml.yaml). (At worst, the [Nimbus experiment delegate](https://searchfox.org/mozilla-central/source/mobile/android/android-components/components/browser/engine-gecko/src/main/java/mozilla/components/experiment/NimbusExperimentDelegate.kt) might need expanded, but I havn't seen something to suggest that yet.) GeckoView: Glad you shared this specific bug! Yes, this should be one of the steps and this bug should be the main part of the GeckoView work. I was wondering if I could just add to the GeckoRuntimeSetting because of this [comment](https://searchfox.org/mozilla-central/rev/396a6123691f7ab3ffb449dcbe95304af6f9df3c/mobile/android/geckoview/src/main/java/org/mozilla/geckoview/RuntimeSettings.java#275). That combined with this bug Agi filed, seems to suggest that a little stronger. Otherwise, it will be setting up something around [here]([GeckoThread.java](https://searchfox.org/mozilla-central/rev/2455e4d6388cbdeadb44b9633b971a65a98b504c/mobile/android/geckoview/src/main/java/org/mozilla/gecko/GeckoThread.java#534)). Gecko: Hopefully we just reusing existing code. These are the enviromental [vars](https://searchfox.org/mozilla-central/rev/e51b2630b44a8836a7ff35a876a2d8b555041d4a/toolkit/xre/nsAppRunner.cpp#978,981) that seem relevant for fission specifically.
>What other Fenix, GV, or Gecko work is needed to listen for enrollment in those (yet to be named) experiments and then enable SHIP or Fission? AC/Fenix: AC side is pretty simple, should just be defining the experiment in [geckoview.fml.yaml](https://searchfox.org/mozilla-central/source/mobile/android/android-components/components/browser/engine-gecko/geckoview.fml.yaml). (At worst, the [Nimbus experiment delegate](https://searchfox.org/mozilla-central/source/mobile/android/android-components/components/browser/engine-gecko/src/main/java/mozilla/components/experiment/NimbusExperimentDelegate.kt) might need expanded, but I havn't seen something to suggest that yet.) GeckoView: Glad you shared this specific bug! Yes, this should be one of the steps and this bug should be the main part of the GeckoView work. I was wondering if I could just add to the GeckoRuntimeSetting because of this [comment](https://searchfox.org/mozilla-central/rev/396a6123691f7ab3ffb449dcbe95304af6f9df3c/mobile/android/geckoview/src/main/java/org/mozilla/geckoview/RuntimeSettings.java#275). That combined with this bug Agi filed, seems to suggest that a little stronger. Otherwise, it will be setting up something around [here]([GeckoThread.java](https://searchfox.org/mozilla-central/rev/2455e4d6388cbdeadb44b9633b971a65a98b504c/mobile/android/geckoview/src/main/java/org/mozilla/gecko/GeckoThread.java#534)). We also need to add a place to connect this new API to listen and change based on the experiment. Gecko: Hopefully we can just reusing existing code, but I wouldn't be surprised if there is a few small changes we need to make. These are the enviromental [vars](https://searchfox.org/mozilla-central/rev/e51b2630b44a8836a7ff35a876a2d8b555041d4a/toolkit/xre/nsAppRunner.cpp#978,981) that seem relevant for fission specifically.
>What other Fenix, GV, or Gecko work is needed to listen for enrollment in those (yet to be named) experiments and then enable SHIP or Fission? AC/Fenix: AC side is pretty simple, should just be defining the experiment in [geckoview.fml.yaml](https://searchfox.org/mozilla-central/source/mobile/android/android-components/components/browser/engine-gecko/geckoview.fml.yaml). (At worst, the [Nimbus experiment delegate](https://searchfox.org/mozilla-central/source/mobile/android/android-components/components/browser/engine-gecko/src/main/java/mozilla/components/experiment/NimbusExperimentDelegate.kt) might need expanded, but I havn't seen something to suggest that yet.) Work planned in bug 1913733. GeckoView: Glad you shared this specific bug! Yes, this should be one of the steps and this bug should be the main part of the GeckoView work. I was wondering if I could just add to the GeckoRuntimeSetting because of this [comment](https://searchfox.org/mozilla-central/rev/396a6123691f7ab3ffb449dcbe95304af6f9df3c/mobile/android/geckoview/src/main/java/org/mozilla/geckoview/RuntimeSettings.java#275). That combined with this bug Agi filed, seems to suggest that a little stronger. Otherwise, it will be setting up something around [here]([GeckoThread.java](https://searchfox.org/mozilla-central/rev/2455e4d6388cbdeadb44b9633b971a65a98b504c/mobile/android/geckoview/src/main/java/org/mozilla/gecko/GeckoThread.java#534)). Work would happen in this bug 1771965. We also need to add a place to connect this new API to listen and change based on the experiment. Work planned in bug 1913733. Gecko: Hopefully we can just reusing existing code, but I wouldn't be surprised if there is a few small changes we need to make. These are the enviromental [vars](https://searchfox.org/mozilla-central/rev/e51b2630b44a8836a7ff35a876a2d8b555041d4a/toolkit/xre/nsAppRunner.cpp#978,981) that seem relevant for fission specifically. I'd file a new bug if something had to happen here.
>What other Fenix, GV, or Gecko work is needed to listen for enrollment in those (yet to be named) experiments and then enable SHIP or Fission? AC/Fenix: AC side is pretty simple, should just be defining the experiment in [geckoview.fml.yaml](https://searchfox.org/mozilla-central/source/mobile/android/android-components/components/browser/engine-gecko/geckoview.fml.yaml). (At worst, the [Nimbus experiment delegate](https://searchfox.org/mozilla-central/source/mobile/android/android-components/components/browser/engine-gecko/src/main/java/mozilla/components/experiment/NimbusExperimentDelegate.kt) might need expanded, but I havn't seen something to suggest that yet.) Work planned in bug 1913733. GeckoView: Glad you shared this specific bug! Yes, this should be one of the steps and this bug should be the main part of the GeckoView work. I was wondering if I could just add to the GeckoRuntimeSetting because of this [comment](https://searchfox.org/mozilla-central/rev/396a6123691f7ab3ffb449dcbe95304af6f9df3c/mobile/android/geckoview/src/main/java/org/mozilla/geckoview/RuntimeSettings.java#275). That combined with this bug Agi filed, seems to suggest that a little stronger. (Right now, I'm not totally sure they are added before initialization. I'll try to narrow that down shortly.) Otherwise, it will be setting up something around [here]([GeckoThread.java](https://searchfox.org/mozilla-central/rev/2455e4d6388cbdeadb44b9633b971a65a98b504c/mobile/android/geckoview/src/main/java/org/mozilla/gecko/GeckoThread.java#534)). Work would happen in this bug 1771965. We also need to add a place to connect this new API to listen and change based on the experiment. Work planned in bug 1913733. Gecko: Hopefully we can just reusing existing code, but I wouldn't be surprised if there is a few small changes we need to make. These are the enviromental [vars](https://searchfox.org/mozilla-central/rev/e51b2630b44a8836a7ff35a876a2d8b555041d4a/toolkit/xre/nsAppRunner.cpp#978,981) that seem relevant for fission specifically. I'd file a new bug if something had to happen here.
>What other Fenix, GV, or Gecko work is needed to listen for enrollment in those (yet to be named) experiments and then enable SHIP or Fission? AC/Fenix: AC side is pretty simple, should just be defining the experiment in [geckoview.fml.yaml](https://searchfox.org/mozilla-central/source/mobile/android/android-components/components/browser/engine-gecko/geckoview.fml.yaml). (At worst, the [Nimbus experiment delegate](https://searchfox.org/mozilla-central/source/mobile/android/android-components/components/browser/engine-gecko/src/main/java/mozilla/components/experiment/NimbusExperimentDelegate.kt) might need expanded, but I havn't seen something to suggest that yet.) Work planned in bug 1913733. GeckoView: Glad you shared this specific bug! Yes, this should be one of the steps and this bug should be the main part of the GeckoView work. I was wondering if I could just add to the GeckoRuntimeSetting because of this [comment](https://searchfox.org/mozilla-central/rev/396a6123691f7ab3ffb449dcbe95304af6f9df3c/mobile/android/geckoview/src/main/java/org/mozilla/geckoview/RuntimeSettings.java#275). That combined with this bug Agi filed, seems to suggest that a little stronger. (Right now, I'm not totally sure they are added before initialization. I'll try to narrow that down shortly.) Otherwise, it will be setting up something around [here]([GeckoThread.java](https://searchfox.org/mozilla-central/rev/2455e4d6388cbdeadb44b9633b971a65a98b504c/mobile/android/geckoview/src/main/java/org/mozilla/gecko/GeckoThread.java#534)). Work would happen in this bug 1771965. We also need to add a place to connect this new API to listen and change based on the experiment. Work planned in bug 1913733, if it is bigger than expected, then it might get a new bug. Gecko: Hopefully we can just reusing existing code, but I wouldn't be surprised if there is a few small changes we need to make. These are the enviromental [vars](https://searchfox.org/mozilla-central/rev/e51b2630b44a8836a7ff35a876a2d8b555041d4a/toolkit/xre/nsAppRunner.cpp#978,981) that seem relevant for fission specifically. I'd file a new bug if something had to happen here.
>What other Fenix, GV, or Gecko work is needed to listen for enrollment in those (yet to be named) experiments and then enable SHIP or Fission? AC/Fenix: AC side is pretty simple, should just be defining the experiment in [geckoview.fml.yaml](https://searchfox.org/mozilla-central/source/mobile/android/android-components/components/browser/engine-gecko/geckoview.fml.yaml). (At worst, the [Nimbus experiment delegate](https://searchfox.org/mozilla-central/source/mobile/android/android-components/components/browser/engine-gecko/src/main/java/mozilla/components/experiment/NimbusExperimentDelegate.kt) might need expanded, but I havn't seen something to suggest that yet.) Work planned in bug 1913733. GeckoView: Glad you shared this specific bug! Yes, this should be one of the steps and this bug should be the main part of the GeckoView work. I was wondering if I could just add to the GeckoRuntimeSetting because of this [comment](https://searchfox.org/mozilla-central/rev/396a6123691f7ab3ffb449dcbe95304af6f9df3c/mobile/android/geckoview/src/main/java/org/mozilla/geckoview/RuntimeSettings.java#275). That combined with this bug Agi filed, seems to suggest that a little stronger. (Right now, I'm not totally sure they are added before initialization. I'll try to narrow that down shortly.) Otherwise, it will be setting up something around [here]([GeckoThread.java](https://searchfox.org/mozilla-central/rev/2455e4d6388cbdeadb44b9633b971a65a98b504c/mobile/android/geckoview/src/main/java/org/mozilla/gecko/GeckoThread.java#534)). Work would happen in this bug 1771965. We also need to add a place to connect this new API to listen and change based on the experiment. Work planned in bug 1913733, if it is bigger than expected, then it might get a new bug. Gecko: Hopefully we can just reusing existing code, but I wouldn't be surprised if there are a few small changes we need to make. These are the enviromental [vars](https://searchfox.org/mozilla-central/rev/e51b2630b44a8836a7ff35a876a2d8b555041d4a/toolkit/xre/nsAppRunner.cpp#978,981) that seem relevant for fission specifically. I'd file a new bug if something had to happen here.
>What other Fenix, GV, or Gecko work is needed to listen for enrollment in those (yet to be named) experiments and then enable SHIP or Fission? AC/Fenix: AC side is pretty simple, should just be defining the experiment in [geckoview.fml.yaml](https://searchfox.org/mozilla-central/source/mobile/android/android-components/components/browser/engine-gecko/geckoview.fml.yaml). (At worst, the [Nimbus experiment delegate](https://searchfox.org/mozilla-central/source/mobile/android/android-components/components/browser/engine-gecko/src/main/java/mozilla/components/experiment/NimbusExperimentDelegate.kt) might need expanded, but I havn't seen something to suggest that yet.) Work planned in bug 1913733. GeckoView: Glad you shared this specific bug! Yes, this should be one of the steps and this bug should be the main part of the GeckoView work. I was wondering if I could just add to the GeckoRuntimeSetting because of this [comment](https://searchfox.org/mozilla-central/rev/396a6123691f7ab3ffb449dcbe95304af6f9df3c/mobile/android/geckoview/src/main/java/org/mozilla/geckoview/RuntimeSettings.java#275). That combined with this bug Agi filed, seems to suggest that a little stronger. (Right now, I'm not totally sure they are added before initialization. I'll try to narrow that down shortly.) Otherwise, it will be setting up something around adding an extra somewhere for [GeckoThread.java](https://searchfox.org/mozilla-central/rev/2455e4d6388cbdeadb44b9633b971a65a98b504c/mobile/android/geckoview/src/main/java/org/mozilla/gecko/GeckoThread.java#534). Work would happen in this bug 1771965. We also need to add a place to connect this new API to listen and change based on the experiment. Work planned in bug 1913733, if it is bigger than expected, then it might get a new bug. Gecko: Hopefully we can just reusing existing code, but I wouldn't be surprised if there are a few small changes we need to make. These are the enviromental [vars](https://searchfox.org/mozilla-central/rev/e51b2630b44a8836a7ff35a876a2d8b555041d4a/toolkit/xre/nsAppRunner.cpp#978,981) that seem relevant for fission specifically. I'd file a new bug if something had to happen here.
>What other Fenix, GV, or Gecko work is needed to listen for enrollment in those (yet to be named) experiments and then enable SHIP or Fission? AC/Fenix: AC side is pretty simple, should just be defining the experiment in [geckoview.fml.yaml](https://searchfox.org/mozilla-central/source/mobile/android/android-components/components/browser/engine-gecko/geckoview.fml.yaml). (At worst, the [Nimbus experiment delegate](https://searchfox.org/mozilla-central/source/mobile/android/android-components/components/browser/engine-gecko/src/main/java/mozilla/components/experiment/NimbusExperimentDelegate.kt) might need expanded, but I havn't seen something to suggest that yet.) Work planned in bug 1913733. GeckoView: Glad you shared this specific bug! Yes, this should be one of the steps and this bug should be the main part of the GeckoView work. I was wondering if I could just add to the GeckoRuntimeSetting because of this [comment](https://searchfox.org/mozilla-central/rev/396a6123691f7ab3ffb449dcbe95304af6f9df3c/mobile/android/geckoview/src/main/java/org/mozilla/geckoview/RuntimeSettings.java#275). That combined with this bug Agi filed, seems to suggest that a little stronger. (Right now, I'm not totally sure they are added before initialization. I'll try to narrow that down shortly.) Otherwise, it will be setting up something around adding an extra somewhere for [GeckoThread.java](https://searchfox.org/mozilla-central/rev/2455e4d6388cbdeadb44b9633b971a65a98b504c/mobile/android/geckoview/src/main/java/org/mozilla/gecko/GeckoThread.java#534). Work would happen in this bug 1771965. We also need to add a place to connect this new API to listen and change based on the experiment. Work planned in bug 1913733, if it is bigger than expected, then it might get a new bug. Gecko: Hopefully, we can just reusing existing code, but I wouldn't be surprised if there are a few small changes we need to make. These are the enviromental [vars](https://searchfox.org/mozilla-central/rev/e51b2630b44a8836a7ff35a876a2d8b555041d4a/toolkit/xre/nsAppRunner.cpp#978,981) that seem relevant for fission specifically. I'd file a new bug if something had to happen here.