Change Details

The visual editor (and the 2017 wikitext editor) emits many `init` events with the platform set to `other`, which shouldn't happen. According to @DLynch: > The `init` platform:other issue is that our tracking code tries to work out the platform via `platform: ve.init && ve.init.target && ve.init.target.constructor.static.platformType || 'other',` > > Unfortunately, almost everywhere that we try to log `init` from hasn't yet loaded the target. Given that most of these are inside `ve.init.mw.DesktopArticleTarget.init.js`, I think we could safely just hardcode `platform: 'desktop'` in those calls. (Look for `trackActivateStart` in that file.)

The visual editor and the 2017 wikitext editor emit many `init` events with the platform set to `other`, which shouldn't happen. According to @DLynch: > The `init` platform:other issue is that our tracking code tries to work out the platform via `platform: ve.init && ve.init.target && ve.init.target.constructor.static.platformType || 'other',` > > Unfortunately, almost everywhere that we try to log `init` from hasn't yet loaded the target. Given that most of these are inside `ve.init.mw.DesktopArticleTarget.init.js`, I think we could safely just hardcode `platform: 'desktop'` in those calls. (Look for `trackActivateStart` in that file.)

The visual editor (and the 2017 wikitext editor) emits many `init` events with the platform set to `other`, which shouldn't happen. According to @DLynch: > The `init` platform:other issue is that our tracking code tries to work out the platform via `platform: ve.init && ve.init.target && ve.init.target.constructor.static.platformType || 'other',` > > Unfortunately, almost everywhere that we try to log `init` from hasn't yet loaded the target. Given that most of these are inside `ve.init.mw.DesktopArticleTarget.init.js`, I think we could safely just hardcode `platform: 'desktop'` in those calls. (Look for `trackActivateStart` in that file.)