Apologies for forgetting to ask this in my last post: 

> As discussed, a 6 months deprecation period

Can we be explicit, which M release/Month will this be presuming the other 
conditions are met.

Thank you,
Greg

On Monday, January 24, 2022 at 8:36:00 AM UTC-8 Daniel Vogelheim wrote:

> Hi again,
>
> On Mon, Jan 24, 2022 at 5:22 PM Daniel Vogelheim <voge...@google.com> 
> wrote:
>
>> Hi Noah,
>>
>> On Thu, Jan 20, 2022 at 8:11 PM Noah Lemen <noah....@gmail.com> wrote:
>>
>>> At Meta (formerly known as Facebook) we have a fair amount of 
>>> dependencies on domain lowering via document.domain. We've discussed this 
>>> internally, and feel that the most difficult aspect of this for us 
>>> currently is identifying where we depend on domain lowering. We feel that 
>>> something that may be helpful for us would be a reporting API not on 
>>> document.domain, but rather on any cross-origin accesses that are only 
>>> working because of domain lowering. Would a reporting API like this be 
>>> possible to add to help us along the deprecation process?
>>
>>
>> This should work as-is. I just tried it out: When warnings are enabled 
>> (i.e., during the 6 milestone warning period), or when 
>> --enable-features=OriginAgentClusterDefaultWarning is used on the current 
>> tip-of-tree build, assigning to document.domain triggers the 
>> deprecation warning (if no other errors interfere). The warning is 
>> delivered through the Reporting API and can be programmatically processed 
>> using ReportingObserver 
>> <https://developer.mozilla.org/en-US/docs/Web/API/ReportingObserver/ReportingObserver>,
>>  
>> For example, the first code snippet in this article 
>> <https://developers.google.com/web/updates/2018/07/reportingobserver> will 
>> successfully report the warning. Is this what you're looking for?
>>
>
> It's been pointed out to me that I've overlooked the "on any accesses that 
> are only working because of domain lowering" bit. That isn't there. I'll 
> see if I can add it. Sorry for misunderstanding.
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5ff6b4e8-8f24-4eb5-8d23-3ad3bc927cden%40chromium.org.

Reply via email to