Why wouldn't this just be another single button, like [Load Full Site] [OK] instead of a checkbox/toggle that alters the ok button? It seems like the mock in the document shows that two-button approach. This toggle is a bit weird.
msw: Note that the strings after full launch make a bit more sense with a toggle / checkbox.
See go/subresource-filter-ui-explanation for links to mocks with better strings.
As charrison mentioned, the strings here are not final. The switch should eventually be labelled "Always show ads on this site", not "Load full site". +srahim
The intention of a switch vs. a button was two-fold:
1. To make clear this action is a permanent opt-out (like a permission). In other contexts where we use a "Load full site" button, its longevity is not clear, but is typically for the remainder of the session.
2. While we want to make disabling ad blocking straightforward, we don't want to make it the primary CTA. Having a button labelled "Always show ads on this site" would be enormous and the first thing people would see when expanding the infobar. We want the focus to be more on *why* ads were blocked, with an opt-out as a safety measure. Using a switch + button accomplished this better, though it adds a second tap.
"flash blocked" UI for context for the "learn more" link. Note that this UI seems completely broken on Mac (with UMA to back it up - no one clicks learn more).
Comment 1 by melandory@chromium.org
, Mar 22 20171.4 MB
1.4 MB View Download
875 KB
875 KB View Download