Change Details

As a user, I want a the language switcher feature readily available to me when I load a page, and not just in beta. This should be scheduled to occur one week after {T128350} is deployed to mobile web beta, in order for the Reading Web extended team to verify the beta version functions adequately in larger scale practice, as is the convention with use of beta on the prod cluster. ##Acceptance criteria [ ] New language switcher affordance (new page action bar at top of page) is deployed at 100% to mobile web stable channel

As a user, I want a the language switcher feature readily available to me when I load a page, and not just in beta. This should be scheduled to occur one week after {T128350} is deployed to mobile web beta, in order for the Reading Web extended team to verify the beta version functions adequately in larger scale practice, as is the convention with use of beta on the prod cluster. ##Acceptance criteria [ ] New language switcher affordance (new page action bar at top of page) is deployed at 100% to mobile web stable channel [] Ensure event logging reflects the new button placement

As a user, I want a the language switcher feature readily available to me when I load a page, and not just in beta. This should be scheduled to occur one week after {T128350} is deployed to mobile web beta, in order for the Reading Web extended team to verify the beta version functions adequately in larger scale practice, as is the convention with use of beta on the prod cluster. ##Acceptance criteria [ ] New language switcher affordance (new page action bar at top of page) is deployed at 100% to mobile web stable channel [] Ensure event logging reflects the new button placement