Here is some initial feedback from an exploratory run on these testcases. I am still working through some other devices/browsers:

Font Changer -
Works:
The settings page is loading. Font changer has a distinct portion of the settings page. Font changer has the desired options. In general, font changes are appearing in articles
Enhancements:

1. Enhancement - It would be nice if the font size on the settings page changed as you chose a new setting to give a visual indication of what the font will be.
2. Possible bug - I was playing with the font setting a bit and ran into a couple of issues. The back button seems to cancel font changes. For example, if the user is reading an article and they decide to change the font size, they have to do this: Tap menu. Tap settings and change font. Tap back. At this point, the font change is canceled. The only workaround is to perform a new search for the same article from the settings page. We may want to add 'done/cancel' buttons or something, or make settings changes persist through browser 'back'.
3. Possible Bug - Font size changes do not seem to effect text in things like lists and infoboxes (some examples below)
4. Staging Issue? - Right now tapping 'send feedback' goes to Nirzar talk page, but I assume that's just because it is on staging.

Font sizes in lists and infoboxes

Expand Sections -
Works:
Setting toggle is present and seems to work. Expand/collapse is working on articles.
Enhancements:

1. Possible Bug - Similar to item #2 above, the back button cancels the setting change.
2. Question - If the user has manually collapsed or expanded sections in an article and then makes the setting change, should those sections expand/collapse? It's seems like a cookie issue, but... Here is what I see right now and it 'looks' possibly correct, but want to check: Toggle expand to on, navigate to an article (Security Article on Staging) and collapse all but one section. Return to settings, toggle expand to off and search for the same article. View the sections. In this case, the one section left expanded remains expanded. Also, if toggled on, then the expanded sections appear on articles. If the user then toggles it off and returns to any of those articles all the sections are still expanded.

Beta Features -
Works:
Toggle is present, Toggling switches the below items to 'locked' or 'checked.'
Enhancements:
Once or twice I managed to get settings into a state where the check or lock icons were missing. I am not sure how to reproduce it right now.

In T184742#3897768, @ABorbaWMF wrote:

Here is some initial feedback from an exploratory run on these testcases. I am still working through some other devices/browsers:

Font Changer -
Works:
The settings page is loading. Font changer has a distinct portion of the settings page. Font changer has the desired options. In general, font changes are appearing in articles
Enhancements:

1. Enhancement - It would be nice if the font size on the settings page changed as you chose a new setting to give a visual indication of what the font will be.
2. Possible bug - I was playing with the font setting a bit and ran into a couple of issues. The back button seems to cancel font changes. For example, if the user is reading an article and they decide to change the font size, they have to do this: Tap menu. Tap settings and change font. Tap back. At this point, the font change is canceled. The only workaround is to perform a new search for the same article from the settings page. We may want to add 'done/cancel' buttons or something, or make settings changes persist through browser 'back'.

@Jdlrobson , @Nirzar - did we overlook this or is it a bug? The back button shouldn't reset the changes.

1. Possible Bug - Font size changes do not seem to effect text in things like lists and infoboxes (some examples below)
2. Staging Issue? - Right now tapping 'send feedback' goes to Nirzar talk page, but I assume that's just because it is on staging.

I'll be setting up the appropriate page for this to go to and post in T182217: Deploy `specialpages` feature branch (promote new Special:MobileOptions, fontchanger etc)

Expand Sections -
Works:
Setting toggle is present and seems to work. Expand/collapse is working on articles.
Enhancements:

1. Possible Bug - Similar to item #2 above, the back button cancels the setting change.
2. Question - If the user has manually collapsed or expanded sections in an article and then makes the setting change, should those sections expand/collapse? It's seems like a cookie issue, but... Here is what I see right now and it 'looks' possibly correct, but want to check: Toggle expand to on, navigate to an article (Security Article on Staging) and collapse all but one section. Return to settings, toggle expand to off and search for the same article. View the sections. In this case, the one section left expanded remains expanded. Also, if toggled on, then the expanded sections appear on articles. If the user then toggles it off and returns to any of those articles all the sections are still expanded.

This is expected behavior

@Jdlrobson , @Nirzar - did we overlook this or is it a bug? The back button shouldn't reset the changes.

In the case of the back button many browsers will send you to the cached page rather than request it again. There's thus no way to actually force this to refresh :/
(Refresh the page and the font size should go into effect - please confirm!)

Previously we redirected to the page after submitting the form but now save is async this is no longer a possibility.

I just tried these steps on reading staging. The settings don't get reverted for me. they do get saved even with back button but you have to refresh the page to see the change take effect.

it's not ideal but there's no other way. I'm fine with this behaviour but @ABorbaWMF should confirm that even with back button it in fact saves the option but does not reflect it without a refresh

@Nirzar - Yes refreshing will reflect the settings changes.

@ABorbaWMF Thanks!

@ovasileva not a bug, but a future feature request?

@Nirzar - during standup, @Jdlrobson suggested that for the time being we move the font switcher back to beta - I've set up T185152: Depromote font switcher back to beta in specialpages feature branch, and we can make a secondary task for feature updates. Perhaps we can just have a toast informing the user to refresh?

After chatting with @Nirzar I've opened T185166 to see if there is some way we can fix this before shipping. If there is, this will be less work then moving the font switcher back into beta.

In T184742#3908185, @Jdlrobson wrote:

After chatting with @Nirzar I've opened T185166 to see if there is some way we can fix this before shipping. If there is, this will be less work then moving the font switcher back into beta.

Sounds good, now prioritized.

I've put the back button fix patch on staging in the hope that it helps us complete testing. It's becoming a pain to have to sync the branch so I'm keen for us to do T182217 ASAP. Let me know if that fixes the problem!

Great! @ABorbaWMF - could you re-test the back button functionality? @Jdlrobson - does T185166: [Spike, 2hrs] Can we detect back button clicks after changing font still need to go through code review? We can keep the QA on here and close both of them together.

@ovasileva I just did a quick test and it looks ok in terms of the back button. I am still seeing this one: "Font size changes do not seem to effect text in things like lists and infoboxes"

@ABorbaWMF - for lists and infoboxes, that it by design. And with that, I believe that concludes QA! Moving to signoff. Looks good to be, but I think @Jdlrobson and @Nirzar should also take a final look before closing.

Specialpages branch also has minor impact [1] on other pages. not sure if we want to test these as the change is very minor but good to have a record of it. I have checked the following special pages and they work as expected

• Nearby
• Log in
• Create account
• Uploads
• Page history
• User contributions
• Changes
• Log (deletion log)

[1] the expected change is the titles of these pages should be larger(than production) and left aligned instead of centre aligned

@ABorbaWMF - do you think you could give one of these (nearby seems to be a good candidate) a very quick look across different browsers? I'm assuming everything is fine, but let's check for the sake of thoroughness.

Anything left to do here?
https://reading-web-staging.wmflabs.org/wiki/Special:MobileOptions is running the latest code and I'm super keen to get this into master asap as the code is starting to converge and become hard to manage given other efforts on other projects e.g. download button.

Working for me so far. I am trying a few different browsers.