New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 835282 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug
Team-Security-UX



Sign in to add a comment

Settings-UI for showing/hiding some ads is confusing

Reported by get...@gmail.com, Apr 20 2018

Issue description

Steps to reproduce the problem:
See two attached screenshots. The "Ads" setting in my Chrome-Android browser seems like it was designed backwards of what would normally be expected.

To be clear, I'm not talking about the default of the setting. I'm talking about the "on" / "off" semantic being backward.

When I first went to this setting, it was in the (normally interpreted) "off" position, and it said "Block some ads...". That sounded like a feature I wanted, so I flipped the toggle to the (normally interpreted) "on" position. The help text then switched to "Show ads".

What is the expected behavior?
I expect that if something is "off", then it's not doing anything, and if it's "on" then it's doing something. I think that's the normal interpretation of toggle switch UI.

What went wrong?
The normal state of the web is that I see ads. If Chrome wants to be helpful and let me block some ads, that's awesome. But "blocking some ads" is a feature I either turn on or off (again, regardless of its default).

It's quite confusing to be presented a UI for a setting to turn "off" a feature of "showing the rest of the ads that were otherwise be blocked."

Did this work before? N/A 

Chrome version: 65.0.3325.181  Channel: n/a
OS Version: OS X 10.11.6
Flash Version:
 
setting-off.png
85.0 KB View Download
setting-on.png
63.4 KB View Download
Cc: rsch...@chromium.org
Components: UI>Browser>AdFilter
Hm yeah I can see how that's confusing. Unfortunately this seems to be the norm for "block"-type settings. For instance, the popup blocking setting can be misinterpreted the same way.
Cc: srahim@chromium.org
Yeah, I believe that's the reason it went this way. Maybe the wording could be improved? +Shimi, any thoughts on what we could do here?
Labels: Needs-triage-Mobile
Cc: xunji...@chromium.org
+xunjieli who was also confused by this UI recently.
I find the wording confusing. My initial thought was that this was a bug and they had the states in reverse. Instead of saying "Ads," the title should be more specific. The "Allowed" sub text is unclear.

One possible revision: 

Block intrusive ads
Block ads from sites that tend to show intrusive ads   [ Default state on]

Block intrusive ads
All ads will be shown    [This should be the off state]
I think the wording on desktop is a lot clearer, maybe the language could be merged.
ads-setting-desktop.png
14.7 KB View Download
Cc: -rsch...@chromium.org
Cc: chelamcherla@chromium.org
Components: UI>Browser>SiteSettings
Labels: Triaged-Mobile
Adding UI>Browser>SiteSettings component for further help in triaging from site settings team.

Thanks!
Owner: patricia...@chromium.org
Status: Assigned (was: Unconfirmed)
Assigning to patricialor, feel free to reassign if appropriate. Thanks!
srahim, can you also weigh in? I feel if this string needs to change, then many settings need to as well. Popups has the exact same confusion.
Owner: engedy@chromium.org
This should probably go to someone in the new permissions team :) +engedy@ as TL for help triaging.
Cc: -srahim@chromium.org -chelamcherla@chromium.org sindhu.chelamcherla@chromium.org engedy@chromium.org
Labels: Hotlist-Permissions
Owner: srahim@chromium.org
@getify, would this sound better to you: "Blocked on sites that tend to show intrusive ads"?

With regards to the ads-setting in particular, I have to agree with the comments from Charlie and Ryan. The ads-setting is phrased consistently with the other permission strings.

However, in general, I do sense the disconnect that some of these settings are worded from the perspective of letting the website do something, and some from the perspective of the browser preventing that via countermeasures.

Sign in to add a comment