Titouan, et.al. Is this still awaiting more feedback, and/or another intent to ship?
This post: https://developer.chrome.com/blog/private-network-access-update/ was brought to my attention by our marketing department, but appears to be concerned with mixed content. (I do not expect our market department to be tech-savy enough to understand the difference) But that update does mention that RFC1918 also addresses *"websites now have to explicitly request a grant from servers on private networks before being allowed to send arbitrary requests."* which would also include this topic. Mixed content won't be an issue our company, but preflight will. Since we have a large installation of devices already out in the wild, our support and marketing team are watching carefully to see if 'preflight' becomes implemented. Because it will generate breakage at a level of a hundred thousand or more, resulting in companies having to re-certify firmware before deploying it (a process that can take up to 9 months). And since I'm still trying to learn how to filter all the groups emails, I'm not sure I understand that I will see when preflight is ready for the next phase. So that is why I ask :-) Thanks. On Tuesday, April 25, 2023 at 10:01:46 AM UTC-5 Scott Weber wrote: > Titouan, > Excellent. > Since I am now subscribed to this blog, I will be aware of these changes. > ( although google SSO used my personal email, not my employer) > > I was (and still am) cautious about getting ALL the changes, since I'm > sure there are hundreds. And our little embedded web server doesn't have > to be concerned with most of them... but that's off topic :-) > > Thanks for the details in my other, off topic, questions as well. > > -Scott > On Tuesday, April 25, 2023 at 7:59:35 AM UTC-5 Titouan Rigoudy wrote: > >> [blink-dev@ to bcc] >> >> Hi Scott, >> >> Thanks for reaching out. Answers inline below. >> >> On Mon, Apr 24, 2023 at 9:32 PM Scott Weber <scott...@gmail.com> wrote: >> >>> Grammar correction, sorry: >>> "a brief tutorial to a newbie on *the status of* PNA and..." >>> >>> On Monday, April 24, 2023 at 2:13:59 PM UTC-5 Scott Weber wrote: >>> >>>> Forgive me if this is not the correct place to ask... >>>> I seem to have stumbled across this conversation trying to find answers >>>> (this thread looks like an email archive chain). >>>> I am new to this platform of getting early information about upcoming >>>> changes. >>>> >>>> Originally, PNA was supposed to "go live" in Version 113. When I heard >>>> about it back in Nov '22, we tested it in Chrome v104 and placed support >>>> in >>>> our firmware back then. >>>> >>>> So, is this now what could be called "on hold" ? >>>> >>> >> The timeline has been paused, but work has not. We are currently working >> on reducing the compatibility impact of the change, i.e. the amount of >> websites that would be broken by it. Were we to enforce that PNA preflights >> must succeed tomorrow, too many existing websites would experience issues. >> >> >>> (while we updated our firmware, there is no assurance the 1000's and >>>> 1000's of devices in the wild are being updated in a timely manner) >>>> >>>> On Thursday, April 6, 2023 at 3:58:02 AM UTC-5 Titouan Rigoudy wrote: >>>> >>>> Just wanted to state here that we'll send a different intent to ship >>>> >>>> >>>> What is "intent to ship" ? And what is meant my "send"? Send to >>>> who? Is there a mailing list? >>>> >>> >> This email thread is entitled "Intent to ship". I sent it to this mailing >> list (blin...@chromium.org) to announce that we were planning to change >> Chromium's web-facing behavior, and to get approval for this change. >> >> See this blog post for an in-depth explanation of Chromium's launch >> process: >> https://blog.chromium.org/2019/11/intent-to-explain-demystifying-blink.html >> >> >>> Titouan and others mention things like M100, M101. Is this the same >>>> designation as version number (v104, and v113). >>>> >>> >> That's right. M stands for milestone. >> >> >>> In summary, my supervisor is asking me to find out if we need to be >>>> ready to tell a plethora of customers they have to upgrade our firmware >>>> when it stops working in the next day or two (or have doc ready telling >>>> them how to disable this requirement). >>>> >>>> Please, could someone give a brief tutorial to a newbie on PNA and how >>>> to be "in the loop" on these things? >>>> >>> >> My previous email was trying to clarify that there will be no further >> changes to PNA preflights without a new Intent to Ship thread and >> associated chromestatus.com feature. Nothing will change in 113, and >> there is no emergency for you to jump on right now. You can stay in the >> loop either by looking at chromestatus.com or by following along on this >> mailing list (blin...@chromium.org). >> >> Cheers, >> Titouan >> >> >>> Thanks. >>>> >>>> -- 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/cd350f07-269d-41cd-81c2-2aa19d959e7en%40chromium.org.
