Change Details

As mentioned in the description of the parent task, we're interested in understanding the impact of these missing tags. We see a couple of approaches to understanding this: 1. Estimate what percent of edits historically have occurred under the circumstances that caused the bug (edits to the first card). This can then be combined with counts of tagged edits from the Data Lake to estimate the actual edits. 2. Use HomepageModule and EditAttemptStep to identify edits that fit these circumstances, but did not have the edit tag applied. From previous investigations, we know that this is challenging partly because HomepageModule is logged client-side and therefore gets blocked by ad blockers. As mentioned in the parent task, this rolled out on 2020-09-15.

As mentioned in the description of the parent task, we're interested in understanding the impact of these missing tags. We see a couple of approaches to understanding this: 1. Estimate what percent of edits historically have occurred under the circumstances that caused the bug (edits to the first card). This can then be combined with counts of tagged edits from the Data Lake to estimate the actual edits. 2. Use HomepageModule and EditAttemptStep to identify edits that fit these circumstances, but did not have the edit tag applied. From previous investigations, we know that this is challenging partly because HomepageModule is logged client-side and therefore gets blocked by ad blockers. As mentioned in the parent task, this rolled out on 2020-09-15. Investigating further, it appears the bug is triggered when the user clicks on the first task shown upon loading the Newcomer Homepage. In that case the URL of the page is incorrect, leading to the "newcomer task" tag not being applied. I've found that if the user is already on the Homepage but takes action that loads up the task list, then the URL is correct. Three ways of making that happen is to either go through the module initialization process, or change the topics or difficulty of the tasks shown.

As mentioned in the description of the parent task, we're interested in understanding the impact of these missing tags. We see a couple of approaches to understanding this: 1. Estimate what percent of edits historically have occurred under the circumstances that caused the bug (edits to the first card). This can then be combined with counts of tagged edits from the Data Lake to estimate the actual edits. 2. Use HomepageModule and EditAttemptStep to identify edits that fit these circumstances, but did not have the edit tag applied. From previous investigations, we know that this is challenging partly because HomepageModule is logged client-side and therefore gets blocked by ad blockers. As mentioned in the parent task, this rolled out on 2020-09-15. Investigating further, it appears the bug is triggered when the user clicks on the first task shown upon loading the Newcomer Homepage. In that case the URL of the page is incorrect, leading to the "newcomer task" tag not being applied. I've found that if the user is already on the Homepage but takes action that loads up the task list, then the URL is correct. Three ways of making that happen is to either go through the module initialization process, or change the topics or difficulty of the tasks shown.