OK, yeah - looks like what I'm seeing is just some sort of 10+-second delay at first startup[1], before interventions get enabled. If I wait a few minutes, I get expected-results on the browserstack environment. So: the intervention is functioning properly here. [1] Here's a profile I captured (started profiling a few seconds after connecting to BrowserStack, so mentally add 5+ seconds to the timestamps in the profile for the "real" timeline): https://share.firefox.dev/4mGkV8v . At around 7.75s in the profile (so maybe t=13s in my real-world experience), the WebExtensions process shows "_onEnabledStateChanged" which seems to kick off some activity that includes various functions with names like `_enableInterventionNow`. I think that's the important thing here for getting the intervention to be active. I'm not sure why there's such a long delay, but maybe BrowserStack happens to be using a Firefox user-profile with stale data for that extension, and we're blocked on remote-settings causing the webcompat extension to dynamically update or become enabled, or something like that.
Bug 1902405 Comment 14 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
OK, yeah - looks like what I'm seeing is just some sort of 10+-second delay at first startup[1], before interventions get enabled. If I wait 30 seconds or so, then I get expected-results on the browserstack environment. So: the intervention is functioning properly here. [1] Here's a profile I captured (started profiling a few seconds after connecting to BrowserStack, so mentally add 5+ seconds to the timestamps in the profile for the "real" timeline): https://share.firefox.dev/4mGkV8v . At around 7.75s in the profile (so maybe t=13s in my real-world experience), the WebExtensions process shows "_onEnabledStateChanged" which seems to kick off some activity that includes various functions with names like `_enableInterventionNow`. I think that's the important thing here for getting the intervention to be active. I'm not sure why there's such a long delay, but maybe BrowserStack happens to be using a Firefox user-profile with stale data for that extension, and we're blocked on remote-settings causing the webcompat extension to dynamically update or become enabled, or something like that.
OK, yeah - looks like what I'm seeing is just some sort of 10+-second delay at first startup[1], before interventions get enabled. If I wait 30 seconds or so, then I get expected-results on the browserstack environment. So: the intervention is functioning properly here. [1] Here's a profile I captured in BrowserStack: https://share.firefox.dev/4mGkV8v (and note that I started profiling a few seconds after connecting to BrowserStack, so mentally add 5+ seconds to the timestamps in the profile, to get my "real-world-experience" timeline). At around 7.75s in the profile (so maybe t=13s in my real-world experience), the WebExtensions process shows "_onEnabledStateChanged" which seems to kick off some activity that includes various functions with names like `_enableInterventionNow`. I think that's the important thing here for getting the intervention to be active. I'm not sure why there's such a long delay, but maybe BrowserStack happens to be using a Firefox user-profile with stale data for that extension, and we're blocked on remote-settings causing the webcompat extension to dynamically update or become enabled, or something like that.