Ah-ha, I see what's going on here. Fennec uses BrowserUITelemetry, whereas we are removing UITelemetry. We are leaving BrowserUITelemetry alone in this process, so Fennec should have no interruption from this part of the effort.
Because of the similar naming (and how, technically, UITelemetry is -also- the name of the service under both of the collections we're discussing) we will spend some extra time in testing and validating to ensure we don't mess with Fennec on this. In short: naming things is hard, Fennec should be fine, we will make sure Fennec won't be affected. :chutten On Mon, Mar 26, 2018 at 4:43 PM, Jan Henning < jh+mobile-firefox-...@buttercookie.de> wrote: > (Used the wrong mai-address for sending, so second attempt) > > And of course there's lots more in the Java code, which that link doesn't > even catch, compare e.g. https://dxr.mozilla.org/ > mozilla-central/search?q=path%3Amobile*java+telemetry+ > uievent&redirect=false > Jan > > Am 26.03.2018 um 22:29 schrieb Chris Hutten-Czapski: > > which instrumented Fennec[1] far more completely than Firefox. > > [...] > > [1]: https://searchfox.org/mozilla-central/search?q=UITelemetry&; > case=false®exp=false&path=mobile > >
_______________________________________________ mobile-firefox-dev mailing list mobile-firefox-dev@mozilla.org https://mail.mozilla.org/listinfo/mobile-firefox-dev
