Correct I'm using .webContent.blockedByFilter for the latter scenario I described (explicitly providing a URL).
I'm using .shield.webDomains for the former. Thanks for the clarification. I feel it's confusing that as developers we have the ability to shield arbitrary domains but not display a relevant message on that shield or modify the behavior of it. It can be unclear to users which app is even generating the shield. I'll file a report. Two follow-up questions:
Can you confirm that the only way to get a WebDomainToken is from a FamilyActivitySelection generated by the user? The reason this is relevant is for non-safari iOS users - the web domains they use frequently in their non-safari browser do not appear in the FamilyActivityPicker.
Is there documentation on how the FamilyActivityPicker selects which WebDomains are present? How far back in user history is used, etc.
Topic:
App & System Services
SubTopic:
General
Tags: