Re: [blink-dev] Re: Intent to Experiment: HTTPS Upgrades

M115 experimentation LGTM On Tue, Jul 11, 2023, 22:53 Chris Thompson wrote: > Quick additional context for this intent: we have previously sent an > Intent-to-Ship for this feature (see > https://groups.google.com/a/chromium.org/g/blink-dev/c/cAS525en8XE/m/OdMMGgLXAgAJ) > but we are separately

Re: [blink-dev] Intent to Ship: Array grouping

LGTM2 On Wed, Jul 12, 2023, 03:27 Mike Taylor wrote: > LGTM1 > On 7/11/23 1:33 PM, Shu-yu Guo wrote: > > Contact emails > s...@chromium.org > > Explainer > https://github.com/tc39/proposal-array-grouping/blob/main/README.md > > Specification https://tc39.es/proposal-array-grouping/ > > Summary

Re: [blink-dev] Intent to Ship: Array grouping

LGTM1 On 7/11/23 1:33 PM, Shu-yu Guo wrote: Contact emails s...@chromium.org Explainer https://github.com/tc39/proposal-array-grouping/blob/main/README.md Specification https://tc39.es/proposal-array-grouping/ Summary Adds news

[blink-dev] Re: Intent to Experiment: HTTPS Upgrades

Quick additional context for this intent: we have previously sent an Intent-to-Ship for this feature (see https://groups.google.com/a/chromium.org/g/blink-dev/c/cAS525en8XE/m/OdMMGgLXAgAJ) but we are separately requesting approval to experiment in M115 Stable as our spec change

[blink-dev] Intent to Experiment: HTTPS Upgrades

Contact emailscth...@chromium.org, dadr...@google.com Explainerhttps://github.com/dadrian/https-upgrade/blob/main/explainer.md Specificationhttps://github.com/whatwg/fetch/pull/1655 Summary Automatically and optimistically upgrade all main-frame navigations to HTTPS, with fast fallback to

[blink-dev] Intent to Ship: Array grouping

Contact emails s...@chromium.org Explainerhttps://github.com/tc39/proposal-array-grouping/blob/main/README.md Specificationhttps://tc39.es/proposal-array-grouping/ Summary Adds news Object.groupBy(iterable, groupCallback) and Map.groupBy(iterable, groupCallback) to perform a grouping or

Re: [blink-dev] Intent to Ship: Private Aggregation API

LGTM3 On Tue, Jul 11, 2023, 17:59 Chris Harrelson wrote: > LGTM2 > > On Mon, Jul 10, 2023, 2:58 PM Mike Taylor wrote: > >> LGTM1 >> On 7/10/23 2:04 PM, Alex Turner wrote: >> >> As a quick update, the WebDriver extension PR has now landed. (Thanks >> Mathias for the review!) So, it should be

Re: [blink-dev] Intent to Ship: Private Aggregation API

LGTM2 On Mon, Jul 10, 2023, 2:58 PM Mike Taylor wrote: > LGTM1 > On 7/10/23 2:04 PM, Alex Turner wrote: > > As a quick update, the WebDriver extension PR has now landed. (Thanks > Mathias for the review!) So, it should be safe to include that change as > part of this I2S. > > On Mon, Jul 10,

Re: [blink-dev] Re: Intent to Ship: HTTPS pages with Cache-control: no-store and Back/Forward Cache

On 7/11/23 2:19 AM, 'Fergal Daly' via blink-dev wrote: [BCC chrome-bfca...@google.com] On Tue, 11 Jul 2023 at 15:16, Mingyu Lei wrote: +chrome-bfcache On Tue, Jul 11, 2023 at 1:08 PM Mingyu Lei wrote: Contact emails

Re: [blink-dev] Intent to Ship: Private Network Access preflight requests for subresources

Do I understand correctly that access to access to private network endpoints from secure contexts (https) is currently not in scope? That's my interpretation of https://developer.chrome.com/blog/private-network-access-update/#cors-preflight-requests which is in "Plans for the future" section.

Re: [blink-dev] Intent to Deprecate: Deprecate unload event

Hello, Hypothesis (https://web.hypothes.is, a web page/PDF/ebook annotation tool) uses the "unload" event to signal to one end of a message channel when the other end is in a frame that is about to go away. This is a workaround for the lack of a "close" event in the Channel Messaging API

[blink-dev] Re: Intent to Ship: HTTPS pages with Cache-control: no-store and Back/Forward Cache

+chrome-bfcache On Tue, Jul 11, 2023 at 1:08 PM Mingyu Lei wrote: > Contact emailskenjibah...@chromium.org, fer...@chromium.org, > denom...@chromium.org, le...@chromium.org > > Specification > https://github.com/fergald/explainer-bfcache-ccns/blob/main/README.md > > Design docs >

[blink-dev] Intent to Ship: HTTPS pages with Cache-control: no-store and Back/Forward Cache

Contact emailskenjibah...@chromium.org, fer...@chromium.org, denom...@chromium.org, le...@chromium.org Specification https://github.com/fergald/explainer-bfcache-ccns/blob/main/README.md Design docs https://docs.google.com/document/d/1qX1w6L6laTzpFTh78dvT7wwC1060Z3he2Azp4BAwsUE/edit?usp=sharing

[blink-dev] Re: Intent to Ship: HTTPS Upgrades

Oh, I see that "bloomberg.com" was added to "net/http/transport_security_state_static.json" in m116... that probably explains it. I can try remove it from the local build. Thanks so much for your help! On Mon, Jul 10, 2023 at 8:24 PM Shezan Baig wrote: > Ahh, I see. Do you know if there is

[blink-dev] Re: Intent to Ship: HTTPS Upgrades

Hi, Is there a way to disable this feature? I tried running the browser with " --disable-features=HttpsUpgrades", but it still seems to be performing these upgrades. Thanks, -shez- On Wednesday, May 24, 2023 at 7:13:38 PM UTC-4 cth...@chromium.org wrote: > Contact emailscth...@chromium.org,

[blink-dev] Re: Intent to Ship: HTTPS Upgrades

I see the following in the netlog: t= 97 [st= 0] TRANSPORT_SECURITY_STATE_SHOULD_UPGRADE_TO_SSL * --> get_sts_state_result = true <--- this is false in the m115 build* --> host = "dsbeta.prod.bloomberg.com" -->

[blink-dev] Re: Intent to Ship: HTTPS Upgrades

I am using a locally built chrome.exe (so not one of the Canary/Dev/Beta channels), and doing the following: 116.0.5845.14/chrome.exe --proxy-server= http:// This causes the to get a "CONNECT :443", which unfortunately the proxy is not currently configured to handle properly (it blocks and

[blink-dev] Re: Intent to Ship: HTTPS Upgrades

Hi, Is there a way to disable this feature? I tried running the browser with " --disable-features=HttpsUpgrades", but it still seems to be performing these upgrades. Thanks, -shez- On Wednesday, May 24, 2023 at 7:13:38 PM UTC-4 cth...@chromium.org wrote: > Contact emailscth...@chromium.org,

[blink-dev] Re: Intent to Ship: HTTPS Upgrades

Ahh, I see. Do you know if there is a switch to disable HSTS? (seems to be a new behavior in m116) Thanks, -shez- On Mon, Jul 10, 2023 at 8:22 PM Chris Thompson wrote: > This indicates that the upgrades are due to HSTS, so this is unrelated to > HTTPS-Upgrades (this new feature).

Re: [blink-dev] Intent to Prototype: CSS font-variant-emoji

Thanks for clarifying the question. On 7/8/23 21:40, Sangwhan Moon wrote: On 2023年07月08日 07時03分10秒 (+09:00), ChangSeok Oh wrote: > How so? Sorry, what is your question? If you were asking why the TAG review status was Not applicable, I have no idea. That is the default text for

[blink-dev] Re: Intent to Ship: HTTPS pages with Cache-control: no-store and Back/Forward Cache

[BCC chrome-bfca...@google.com] On Tue, 11 Jul 2023 at 15:16, Mingyu Lei wrote: > +chrome-bfcache > > On Tue, Jul 11, 2023 at 1:08 PM Mingyu Lei wrote: > >> Contact emailskenjibah...@chromium.org, fer...@chromium.org, >> denom...@chromium.org, le...@chromium.org >> >> Specification >>