Re: [blink-dev] Re: Intent to extend the origin trial: WebTransport over HTTP/3

On Thu, Oct 28, 2021 at 2:38 AM Joe Medley wrote: > Hi, > > Can I get some clarification? > > So this extends the origin trial through 96, but you don't know yet > whether it will ship in 97? Is this correct? > We're shipping WebTransport over HTTP/3 in 97. > Joe > Joe Medley | Technical Writer

[blink-dev] Intent to Extend Origin Trial: Subresource loading with Web Bundles

Contact emails hay...@chromium.org, denom...@chromium.org Explainer https://github.com/WICG/webpackage/blob/master/explainers/subresource-loading.md Specification Design docs https://chromium.googlesource.com/chromium/src.git/+/refs/heads/master/content/browser/web_package/subresource_loading_

Re: [blink-dev] Re: Intent to Deprecate: TLS 1.0 and TLS 1.1

Hi. Thank you for your reply. This error happened in the night of October 22nd. While I was checking my google forms and gmail. I am using Avast as my antivirus software and my OS is windows 10. I just checked my antivirus software and found out that one of their services has expired. I tried to

Re: [blink-dev] RE: [EXTERNAL] Re: Intent to Implement and Ship: Feature policy for Keyboard API

For a cross origin renderer the browser process would be involved because the allow attribute restriction is in one renderer, and the enforcement of the permission is in the renderer that wants to use it. I do not think it is difficult to check the policy on the mojo request of the keyboard map in

RE: [blink-dev] RE: [EXTERNAL] Re: Intent to Implement and Ship: Feature policy for Keyboard API

I'm not sure if checking that in the browser would make sense here because the allow attribute restriction is specified in the DOM and the browser process isn't involved. I did ask this in the slack channel and pretty much got the same response that the renderer should be enforcing this check. I

Re: [blink-dev] Intent to Deprecate and Remove: WebSQL in third-party contexts

Sorry for the delay, the data for actually reading/writing a database (as opposed to opening it ) in a third party context ended up being nearly identical (

Re: [blink-dev] RE: [EXTERNAL] Re: Intent to Implement and Ship: Feature policy for Keyboard API

I was looking at the implementation of this. Is it possible to move the check of the policy to be based in the browser when the map is fetched? As of right now the policy enforcement is on the renderer side, so a compromised renderer can request the keyboard map. dave. On Wed, Oct 27, 2021 at 4:5

Re: [blink-dev] Intent to Prototype and Ship: self.structuredClone

This is amazing! :) I agree it shouldn't block this, but do we have anywhere written what are the browser's differences on structured clone algorithms? Is it a spec issue? Could we add WPT tests for it? On Wed, Oct 27, 2021 at 2:45 PM Andreu Botella wrote: > * Contact emails* > and...@andreubot

RE: [blink-dev] RE: [EXTERNAL] Re: Intent to Implement and Ship: Feature policy for Keyboard API

Created an issue to get feedback from TAG: https://github.com/w3ctag/design-reviews/issues/685 I added this to the webappsec-permission policy: https://github.com/w3c/webappsec-permissions-policy/pull/428, but will also create an issue to investigate Permissions API integration. Thanks! From: A

[blink-dev] Intent to Prototype and Ship: self.structuredClone

* Contact emails* and...@andreubotella.com, jbro...@chromium.org, su...@chromium.org *Explainer* https://github.com/whatwg/html/issues/793 *Specification* https://html.spec.whatwg.org/#structured-cloning * Summary* Enables using the HTML structured clone algorithm synchronously for cloning a

RE: [EXTERNAL] Re: [blink-dev] Intent to Implement and Ship: Add support for Promise to Blobs in clipboard item

Thanks Daniel for raising this concern. I have opened an issue to discuss with the Editing WG: https://github.com/w3c/clipboard-apis/issues/161. In the current implementation, I think verifying whether the Document is active or not after the promises have been resolved should mitigate some of th

Re: [blink-dev] Re: Intent to extend the origin trial: WebTransport over HTTP/3

Hi, Can I get some clarification? So this extends the origin trial through 96, but you don't know yet whether it will ship in 97? Is this correct? Joe Joe Medley | Technical Writer, Chrome DevRel | jmed...@google.com | 816-678-7195 *If an API's not documented it doesn't exist.* On Mon, Oct 25

Re: [blink-dev] Intent to Ship: Standardize existing client hint naming

The code is all in for M97 On Wed, Oct 27, 2021 at 10:30 Joe Medley wrote: > Hi, > > In which version of Chrome do you expect to ship? > > Joe > Joe Medley | Technical Writer, Chrome DevRel | jmed...@google.com | > 816-678-7195 > *If an API's not documented it doesn't exist.* > > > On Thu, Oct

Re: [blink-dev] Intent to Ship: Standardize existing client hint naming

Hi, In which version of Chrome do you expect to ship? Joe Joe Medley | Technical Writer, Chrome DevRel | jmed...@google.com | 816-678-7195 *If an API's not documented it doesn't exist.* On Thu, Oct 21, 2021 at 12:37 PM Alex Russell wrote: > LGTM3. > > In future, if you assert a TAG review is

Re: [blink-dev] Intent to Ship: Independent/Individual Properties for CSS Transforms

Hi, In which version of Chrome do you hope to ship? Joe Joe Medley | Technical Writer, Chrome DevRel | jmed...@google.com | 816-678-7195 *If an API's not documented it doesn't exist.* On Thu, Oct 21, 2021 at 12:03 PM Manuel Rego Casasnovas wrote: > LGTM3. > > On 21/10/2021 19:53, Daniel Brat

Re: [blink-dev] Intent to Implement and Ship : onsecuritypolicyviolation event handler IDL attribute

Hi, In which version of Chrome do you hope to ship? Joe Medley | Technical Writer, Chrome DevRel | jmed...@google.com | 816-678-7195 *If an API's not documented it doesn't exist.* On Thu, Oct 21, 2021 at 11:14 AM Daniel Bratell wrote: > Indeed, so I'm making my LGTM2 on the other thread into

Re: [blink-dev] Re: Intent to Deprecate: TLS 1.0 and TLS 1.1

Hi all, The other possibility could be OS related. I've had this issue with Chromium on old versions macOS specifically, though I've seen it happen on Windows too. Claire - what version of your operating system are you running? Cheers, -slade On Wed, Oct 27, 2021 at 10:50 AM David

[blink-dev] Re: Intent to Deprecate: TLS 1.0 and TLS 1.1

Hi. I would like to know that all of my google services on browser in my pc has some problems regarding this. I can't open google forms, spreadsheets and even my drive has a warning signs of NET:ERR_SSL_OBSOLUTE_VERSION . How will it be fix? Can you help me? On Wednesday, October 17, 2018 at 5:

[blink-dev] Re: Intent to implement: WebRTC SVC extensions

Any update? On Thursday, August 8, 2019 at 10:20:00 PM UTC+3 gur...@microsoft.com wrote: > LGTM. In the past Microsoft Edge has supported this for H.264 via ORTC and > really helped for conferencing scenarios especially on low end devices with > limited resources. Look forward to this! > > > On

Re: [blink-dev] Re: Intent to Deprecate: TLS 1.0 and TLS 1.1

No, the TLS version negotiated should not be OS-dependent. Chrome does not use the OS's TLS stack. If you're seeing an issue that's specific to an older version, could you file a bug so we can take a look? Perhaps you have an antivirus or other local proxy that has been configured to terminate TLS

[blink-dev] Re: Intent to Deprecate: TLS 1.0 and TLS 1.1

Google servers have long supported TLS 1.2, so there is probably some (very) outdated antivirus or proxy on your computer or network that has been configured to decrypt your encrypted browsing activity. You'll want to either disable that or get it updated. If this doesn't ring a bell, we can try t

[blink-dev] Re: Intent to Ship: CSS Color Adjust: 'only' keyword for color-scheme

On Wed, Oct 27, 2021 at 4:09 PM Rune Lillesveen wrote: > > Debuggability > > The existing property and the new keyword should automatically be > supported in devtools. There is possibly a need for force dark / > color-scheme override debugging support in devtools, but that is out of > scope for t

[blink-dev] Intent to Ship: CSS Color Adjust: 'only' keyword for color-scheme

Contact emailsfuth...@chromium.org Specificationhttps://drafts.csswg.org/css-color-adjust/#color-scheme-prop Summary The 'only' keyword has been re-added to the specification for color-scheme as a way of per-element opt-out of color-scheme override like forced darkening. Previously, both declar

Re: [blink-dev] Intent to Extend Experiment: Capture Handle

Thank you, Yoav, for this suggestion about resetting the clock. We would like to now do just that, pausing the experiment 2021-11-01 to 2021-11-21, and restarting it again on 2021-11-22. We would like to experiment for 4 milestones (96 to 99, inclusive). However, if it's possible to also have t

[blink-dev] Intent to Experiment: Web app launch handler

Contact emailsalancut...@chromium.org, mgi...@chromium.org Explainerhttps://github.com/WICG/sw-launch/blob/main/launch_handler.md Summary Adds a "launch_handler" app manifest member that enables web apps to customise their launch behaviour across all types of app launch triggers. Example usage:

Re: [blink-dev] Intent to Prototype: Capability Delegation

This is spec is probably written with the assumption that Permission Delegation is implemented (or should be implemented) in all browsers. However, Permission Delegation is not a Web Standard, an