Change Details

== Background As part of rolling out the sticky header feature with edit buttons, we want to make sure that edit button clicks are captured in the `EditAttemptStep` instrument (see T298518). == Acceptance criteria [] Once edit buttons are included in the sticky header, edit clicks are logged correctly in `EditAttemptStep`

This task involves the work of adding a new event to track when people click on the edit affordances ({nav [[ ]]} and {nav ✏️}) being introduced within the site-wide sticky header. === Requirements - The necessary event(s) are added to `EditAttemptStep` that enables us to track: -- Edit sessions initiated via clicks on the edit affordances present within the site-wide sticky header -- The editing interface people used the edit affordance within the site-wide sticky header to open NOTE: As @MNeisler noted offline, the requirements above will likely require //one// new event [rather than two] considering we will be able to know the editing interface people are using a particular edit affordance within the sticky header to open by way of `EditAttemptStep`'s existing `editor_interface` field. == Background As part of rolling out the sticky header feature with edit buttons, we want to make sure that edit button clicks are captured in the `EditAttemptStep` schema (see T298518). === Minimal test case //TBD// == Acceptance criteria [] Once edit buttons are included in the sticky header, edit clicks are logged in `EditAttemptStep` in a way that meets the `===Requirements` above [] QA verifies the new event(s) added as part of this task are being emitted as expected by clients

== BackgroundThis task involves the work of adding a new event to track when people click on the edit affordances ({nav [[ ]]} and {nav ✏️}) being introduced within the site-wide sticky header. As part of rolling out the sticky header feature with edit buttons, we want to make sure that edit button clicks are captured in the `EditAttemptStep` instrument (see T298518).=== Requirements - The necessary event(s) are added to `EditAttemptStep` that enables us to track: -- Edit sessions initiated via clicks on the edit affordances present within the site-wide sticky header -- The editing interface people used the edit affordance within the site-wide sticky header to open == Acceptance criteriaNOTE: As @MNeisler noted offline, the requirements above will likely require //one// new event [rather than two] considering we will be able to know the editing interface people are using a particular edit affordance within the sticky header to open by way of `EditAttemptStep`'s existing `editor_interface` field. == Background As part of rolling out the sticky header feature with edit buttons, we want to make sure that edit button clicks are captured in the `EditAttemptStep` schema (see T298518). === Minimal test case //TBD// == Acceptance criteria [] Once edit buttons are included in the sticky header, edit clicks are logged correctly in `EditAttemptStep`in `EditAttemptStep` in a way that meets the `===Requirements` above [] QA verifies the new event(s) added as part of this task are being emitted as expected by clients