Drive-by API design comments:
Was this run past the TAG? Did they ask this is not adding a way to return
a stream? And was there a discussion of a setter API that supports streams?
It would be disappointing if we added new surface of this sort without
resolving the core data type issues.
Best,
Contact emailsmas...@chromium.org
Explainerhttps://github.com/whatwg/html/issues/8867#issuecomment-1856696628
Specificationhttps://html.spec.whatwg.org/#dom-element-gethtml
Summary
The prototype implementation (which was shipped in 2020 and then
shape-changed in 2023) contained a method called
>
> I seem to recall that Android Chrome is also limited here, but maybe that
> has changed and my knowledge is outdated.
>
Correct, we don't usually create out-of-process iframes on Android Chrome
if the device has less than 2G of RAM. Otherwise we allow it (e.g.,
for partial
Site Isolation
On Thu, Apr 4, 2024 at 12:11 PM Charlie Reis wrote:
> My understanding is that at least this behavior is deterministic, right?
>> That is, either the same-origin frames will be able to script each other or
>> they won't and this will happen consistently (based on the agent cluster
>> key).
>>
>
The last launch gate approval came in today.
Thanks!
On Wed, Apr 3, 2024 at 11:49 AM Thomas Guilbert
wrote:
> I agree that this would have been a viable solution, and this was
> considered and discussed with the spec editors too [1]. These Opus flags
> were originally supposed to be
Yes, the intention is to allow coordination of experimentation with another
origin trial for Page-Embedded Permissions Controls. I am CCing +Chris
Harrelson and +Rick Byers who
I've discussed the background for this request.
More detailed reasoning is covered in the "motivation" part of the
Contact emails
pauljen...@chromium.org, behamil...@google.com
Explainer
Chrome:
https://github.com/WICG/turtledove/blob/main/FLEDGE_browser_bidding_and_auction_API.md
Services:
https://github.com/privacysandbox/fledge-docs/blob/main/bidding_auction_services_api.md
Note that this explainer has
>
> My understanding is that at least this behavior is deterministic, right?
> That is, either the same-origin frames will be able to script each other or
> they won't and this will happen consistently (based on the agent cluster
> key).
>
Yes, I think it would be deterministic based on the
This does sound a bit unfortunate. My understanding is that at least this
behavior is deterministic, right? That is, either the same-origin frames
will be able to script each other or they won't and this will happen
consistently (based on the agent cluster key).
An observation I had is that it
LGTM2 to continue the Deprecation Trial until M138.
Thanks for pushing this through! It'd be great if by the time this trial
expires we'd have a clearer picture of the required replacement mechanisms
and some momentum for moving trial participants off to them.
On Thu, Apr 4, 2024 at 3:21 PM
Hi Yoav,
The X-Requested-With header exposes the app package name of the embedding
application on all HTTP requests made from WebView. The header value is not
signed, and can be changed either by web content loaded in the WebView, or
by the host app, through various well known methods.
Media
On Thu, Apr 4, 2024 at 1:22 AM Mike Taylor wrote:
> Hi Fredrik,
>
> Just to confim - this is adding support for a new `color-interpolation`
> property value, yes (vs a bugfix or behavior change to an existing
> feature)? If so, can you send an Intent to Ship rather than a PSA?
>
No, it's
12 matches
Mail list logo
