Hello Yaseen, On Thu, Jul 14, 2022 at 8:13 AM Yaseen Khan <yasee...@gmail.com> wrote:
> Hi Daniel, > > Thanks for your quick update. Here is the below different deprecated > warning message in M100 to M102 and M103. > > *M100/M101/M102:* > Relaxing the same-origin policy by setting "document.domain" is > deprecated, and will be disabled by default* in M106, around September > 2022*. To continue using this feature, please opt-out of origin-keyed > agent clusters by sending an Origin-Agent-Cluster: ?0 header along with the > HTTP response for the document and frames. > > *Latest M103:* > Relaxing the same-origin policy by setting document.domain is deprecated, > and will be disabled by default. To continue using this feature, please > opt-out of origin-keyed agent clusters by sending an Origin-Agent-Cluster: > ?0 header along with the HTTP response for the document and frames. > This is due to a general change in the issues panel in DevTools, which has occured around the same time. The target milestone should be displayed separately. In my version, M103, there's a link "Learn more: This change will go into effect with milestone 106." Thanks to your feedback, however, I noticed that I had forgotten to update that milestone when making the other changes. I've now submitted a CL to mark the 'document.domain' issue as scheduled for M109 (rather than M106). So from the next version on - should be M105 - this should correctly state 109. Thanks, Daniel > Regards, > > Yaseen > > On Wednesday, 13 July 2022 at 21:21:10 UTC+5:30 Daniel Vogelheim wrote: > >> Hello Yaseen, >> >> On Wed, Jul 13, 2022 at 2:47 PM Yaseen Khan <yase...@gmail.com> wrote: >> >>> Hi Team, >>> >>> Earliar chromium browser was displaying an error message as >>> *document.domain* is going to deperecated in *M106*. Now I can not see >>> this message and in some blogs postpone to *M109*. Could you confirm on >>> this - when does this actually would enabled and in which version. It would >>> be great if you could share dates for better planning to mitigate this very >>> high risk in our platform. >>> >> >> As written earlier in this thread, the deprecation of document.domain, >> aka defaulting origin-agent-cluster: to ?1, is scheduled for M109. This is >> slightly postponed from the original plan at M106. >> https://chromiumdash.appspot.com/schedule provides a schedule that maps >> versions to planned release dates. >> >> The warning/"issue" in the DevTools issues panel should be active. I'm >> surprised the message would have disappeared. It should occur whenever >> document.domain is set, as well as when an access based on a modified >> document.domain is made. If you have any reproducible case that shows the >> warning isn't shown even though it should be, I'll gladly investigate. >> >> This is scheduled for M109, but note that API owners will have the final >> call of whether and when to launch this. >> > -- 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/CALG6KPMbfz0gU%2B5_eD8Jh93_BpH4xEnYBNjXyGYW1tpn24BtcA%40mail.gmail.com.
