Thank you for the update and cleanup Ben. Also thank you very much for all
your hard work trying to balance very difficult competing goals, engaging
openly with constructive criticism and reevaluating the approach.
Personally, I'm still optimistic that we (the open web community) will find
ways
I appreciate the problems and am disappointed that the project was
abandoned.
I come from a different space, the Open Wallet Foundation, where a very
similar problem is evolving (see the IETF RATS efforts as an example). In
my view the problem is that the client should not need to trust the
See https://github.com/whatwg/urlpattern/pull/198; tracked in
https://chromestatus.com/feature/6076647526891520 and
https://bugs.chromium.org/p/chromium/issues/detail?id=1468446.
The following changes apply to patterns which are constructed using a base
URL, the constructor string syntax, or both
Hey all,
Thanks for your patience. After carefully considering all your feedback,
we’ve decided to no longer pursue the Web Environment Integrity proposal.
The Android team will instead be experimenting with a narrowly scoped
WebView only feature that won’t make it to web browsers. The full
Requesting API owners review.
--
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
On Wed, Nov 1, 2023 at 2:41 AM Elijah Grey wrote:
> Hey all,
>
> Note: If future versions of this API re-use the Element.prototype.setHTML
> method in new ways, there may be potential for breakage. Transcend ships a
> popular client-side firewall tool called airgap.js that regulates (wraps)
>
It will be after you click the button to start an API owners review. Also
don't forget to start the other 5 review categories.
On Thu, Nov 2, 2023 at 9:01 AM Mustaq Ahmed wrote:
> Hi Chris:
>
> https://chromestatus.com/feature/6266812908175360 is the new entry for
> this feature (because
Hi Chris:
https://chromestatus.com/feature/6266812908175360 is the new entry for this
feature (because feature type is read-only). The review bits should now be
visible to API Owners, please let know if that's not the case.
Mustaq
On Fri, Oct 27, 2023 at 5:03 PM Chris Harrelson
wrote:
> Hi
On Wed, Nov 1, 2023 at 11:11 AM Stephen Chenney
wrote:
> Answers inline. Regarding Ander's comment on the current base_feature
> setting: I'll fix that.
>
> Cheers,
> Stephen.
>
> On Wed, Nov 1, 2023 at 4:17 AM Yoav Weiss wrote:
>
>>
>>
>> On Tue, Oct 31, 2023 at 1:45 PM Stephen Chenney
>>
