This is a fascinating proposal. I had no idea about this nonstandard
DownloadURL format.
Although it is not necessary at the prototype stage, as part of shipping
this, it will probably be necessary to write a spec for both the original
DownloadURL feature and this new extension to it.
On Thu, Aug
On Mon, Aug 18, 2025 at 11:16 AM Alex Russell
wrote:
> Hey Mohamed,
>
> We generally expect explainers to be updated throughout the life of a
> feature. LGTM1, conditional on the explainer being updated with up-to-date
> example code for both the problem and proposed solution.
>
Also, FWIW, the
Contact emails
joone...@microsoft.com, jo...@chromium.org
Explainer
https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/DownloadURL/explainer.md
Specification
None
Design docs
https://docs.google.com/document/d/1nHPDuEE876RMKwYBVzWgPvsek-9X1NhZuFyY5Q5Z6YU/edit?usp=sharing
Summary
The [spec PR](https://github.com/w3c/aria/pull/2577) has a couple of LGTMs,
including an approval from one of the chairs for the Aria Working group,
Valerie Young. All comments have been editorial in nature, and I am getting
strong positive signals from the group when the feature is brought up i
LGTM3
On Wed, Aug 20, 2025 at 5:21 PM Alex Russell
wrote:
> LGTM2
>
> On Wednesday, August 20, 2025 at 12:57:06 AM UTC-7 Yoav Weiss wrote:
>
>> LGTM1
>>
>> This seems like a useful addition and the HTML PR work + webkit support
>> makes me hopeful it will be interoperable shortly after landing.
LGTM2
On Wednesday, August 20, 2025 at 12:57:06 AM UTC-7 Yoav Weiss wrote:
> LGTM1
>
> This seems like a useful addition and the HTML PR work + webkit support
> makes me hopeful it will be interoperable shortly after landing.
> Please land the HTML PR before shipping, as I don't think anything i
I see that "Mechanisms are being added to help reduce the risk of
ecosystem-scale abuse of real-world identity (see
https://docs.google.com/document/u/1/d/1L68tmNXCQXucsCV8eS8CBd_F9FZ6TNwKNOaFkA8RfwI/edit)."
Are those mitigations implemented in the version you're planning to ship?
If not, what's th
LGTM3
On Wednesday, August 20, 2025 at 8:16:58 AM UTC-7 yoav...@chromium.org
wrote:
> LGTM2
>
> On Wed, Aug 20, 2025 at 5:13 PM Alex Russell
> wrote:
>
>> Thank you! LGTM1.
>>
>> On Tuesday, August 19, 2025 at 4:41:51 AM UTC-7 Johannes Kron wrote:
>>
>>> Hi Alex,
>>>
>>> Thanks for the feedbac
LGTM2
On Wed, Aug 20, 2025 at 5:13 PM Alex Russell
wrote:
> Thank you! LGTM1.
>
> On Tuesday, August 19, 2025 at 4:41:51 AM UTC-7 Johannes Kron wrote:
>
>> Hi Alex,
>>
>> Thanks for the feedback. I've updated the explainer to move a code
>> example to the beginning of the proposal and have also
Thank you! LGTM1.
On Tuesday, August 19, 2025 at 4:41:51 AM UTC-7 Johannes Kron wrote:
> Hi Alex,
>
> Thanks for the feedback. I've updated the explainer to move a code example
> to the beginning of the proposal and have also added examples for the
> considered alternatives.
>
> Best,
> Johanne
Given the plans for scoped view transitions (which I'm very excited
about!), can there be more than one of these? Should it be an array or an
interable?
Best,
Alex
On Wednesday, August 20, 2025 at 8:05:19 AM UTC-7 Vladimir Levin wrote:
> Yes, there's a resolution on CSSWG
> https://github.co
LGTM3
I'd have loved getting more feedback from the broader community on this,
but given the fact that the team is willing to ship breaking changes to the
feature based on future feedback, that's an acceptable risk.
On Wednesday, August 20, 2025 at 5:02:20 AM UTC+2 Rick Byers wrote:
> On Tue,
Very happy to see us approaching interoperability on this feature!
Looking at
https://wpt.fyi/results/webrtc-encoded-transform?label=experimental&label=master&aligned
there are quite a lot of failures in all browsers. Does wpt.fyi reflect
the test results we'll have after enabling this, and are th
Yes, there's a resolution on
CSSWG https://github.com/w3c/csswg-drafts/issues/12407#issuecomment-3129024378
We're working on the spec PR to add this to the spec
Thanks,
Vlad
On Monday, August 4, 2025 at 2:13:21 PM UTC-4 dan...@microsoft.com wrote:
> Does this still need to be added to a spec?
LGTM3
On Tuesday, August 19, 2025 at 10:18:18 AM UTC-4 Mike Taylor wrote:
> LGTM2
> On 8/18/25 2:21 p.m., Alex Russell wrote:
>
> LGTM1
>
> On Thursday, August 14, 2025 at 1:43:48 PM UTC-7 Chromestatus wrote:
>
>> Contact emails pcho...@google.com
>>
>> Explainer
>> https://github.com/WICG/WebA
On 8/11/25 5:27 a.m., Yoav Weiss (@Shopify) wrote:
Reviving this thread, as while talking to folks about deploying this I
realized we should name `__HostHttp-` to be `__Host-Http-`.
That makes sure that deploying __Host-Http- prefixed cookies maintains
host semantics in non-supporting browsers
On 8/20/25 10:42 a.m., Yoav Weiss (@Shopify) wrote:
On Wed, Aug 20, 2025 at 4:35 PM Mike Taylor
wrote:
On 8/11/25 5:27 a.m., Yoav Weiss (@Shopify) wrote:
Reviving this thread, as while talking to folks about deploying
this I realized we should name `__HostHttp-` to be `__Host
On Wed, Aug 20, 2025 at 4:35 PM Mike Taylor wrote:
> On 8/11/25 5:27 a.m., Yoav Weiss (@Shopify) wrote:
>
> Reviving this thread, as while talking to folks about deploying this I
> realized we should name `__HostHttp-` to be `__Host-Http-`.
> That makes sure that deploying __Host-Http- prefixed c
LGTM1
This seems like a useful addition and the HTML PR work + webkit support
makes me hopeful it will be interoperable shortly after landing.
Please land the HTML PR before shipping, as I don't think anything is
blocking it.
On Wed, Aug 20, 2025 at 9:42 AM Noam Rosenthal
wrote:
> Contact email
Contact emails
jap...@chromium.org, dome...@chromium.org, nrosent...@chromium.org
Explainer
https://github.com/WICG/navigation-api#precommit-handlers
Specification
https://github.com/whatwg/html/pull/10919
Summary
Normally, when navigateEvent.intercept() is called, the intercepted
navigation
20 matches
Mail list logo
