melandory: Could you add details here then? As someone who shares responsibility for code you are touching I feel like it's important to understand what exactly this will be doing.
finnur: The above mocks are just the current implementation, you are correct. Please see go/subresource-filter-ui-explanation for links to the end-state mocks.
We're still working on finalizing strings, and we can't publish anything in the public repo until we've made a public announcement. Since we're hoping to ship soon after the announcement is made we're hoping to get most of the engineering work out of the way using placeholder strings + icons.
Does this make sense?
Uh, last I heard we weren't going to expose this to users. Do we expect them to know what a "Subresource filter" is?
(My first guess as a savvy user would be that it's an ad blocker.)
What's the reason for calling it "subresource filter" internally, then?
There are a lot of things in Chrome that filter subresources already, and I'm concerned about clarity of related code without context. :-/
Yeah, it is kind of confusing. The name was chosen a while ago as the name of the component (in src/components/subresource_filter), but we've only recently started surfacing it in placeholder strings in e.g. content settings.
Hopefully this will be resolved relatively soon when the feature is announced, but if you feel that the placeholder strings are too confusing I can try to come up with something else.
May I ask why we're adding custom sections at the top rather than showing them in the permission section?
The disjoint sections imply me that we're trying to describe different tings to the user, when we should really just be able to explain it once, well.
lgarron: 100% agree with you. It's just that this is the UI we are currently using for things like that (see the location bar). We don't have the facility to show explanatory text right now in site details and we've never had mocks for it. We should do that, but it felt bad to conflate it with launching this feature.
Comment 1 by melandory@chromium.org
, Feb 7 2017