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

[Yoav Weiss]

Thanks for clarifying that. The break in the OT provides us with a
guarantee that it has not been burnt in.


LGTM to experiment m103-m104, given the OT feedback provided on the other
thread.

On Wed, May 25, 2022 at 12:47 PM Daisuke Enomoto 
wrote:

> I would like to make it clear that the previous OT has expired in M101 and
> it's not enabled in M102. So this intent is to enable it back for 103
> through 104.
>
> Daisuke
>
> On Wed, May 25, 2022 at 12:30 PM Daisuke Enomoto 
> wrote:
>
>> Contact emails
>>
>> hay...@chromium.org, denom...@chromium.org
>>
>> Explainer
>>
>>
>> https://github.com/WICG/webpackage/blob/master/explainers/subresource-loading.md
>>
>> Specification
>>
>> https://wicg.github.io/webpackage/subresource-loading.html
>>
>> Design docs
>>
>>
>> https://chromium.googlesource.com/chromium/src.git/+/refs/heads/master/content/browser/web_package/subresource_loading_origin_trial.md
>>
>> Summary
>>
>> We sent the I2S
>> 
>> for the Subresource loading with Web Bundles on April 13th and received a
>> couple of critical feedback we should address before moving forward. While
>> we’re actively engaged with various stakeholders to address them, we
>> realized the previous OT
>> 
>> had expired in M101, which caused an unintended negative impact to the OT
>> participants in that they couldn’t continue to test their changes to use
>> the new format. Therefore, we’re sending this Intent to Extend OT to allow
>> them to check for the possibility of regressions introduced with the
>> changes. The features added in the previous OT are listed below. From the
>> implementation perspective, there is no difference between the previous OT
>> and this time.
>>
>>
>>1.
>>
>>

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

[Daisuke Enomoto]

I would like to make it clear that the previous OT has expired in M101 and
it's not enabled in M102. So this intent is to enable it back for 103
through 104.

Daisuke

On Wed, May 25, 2022 at 12:30 PM Daisuke Enomoto 
wrote:

> Contact emails
>
> hay...@chromium.org, denom...@chromium.org
>
> Explainer
>
>
> https://github.com/WICG/webpackage/blob/master/explainers/subresource-loading.md
>
> Specification
>
> https://wicg.github.io/webpackage/subresource-loading.html
>
> Design docs
>
>
> https://chromium.googlesource.com/chromium/src.git/+/refs/heads/master/content/browser/web_package/subresource_loading_origin_trial.md
>
> Summary
>
> We sent the I2S
> 
> for the Subresource loading with Web Bundles on April 13th and received a
> couple of critical feedback we should address before moving forward. While
> we’re actively engaged with various stakeholders to address them, we
> realized the previous OT
> 
> had expired in M101, which caused an unintended negative impact to the OT
> participants in that they couldn’t continue to test their changes to use
> the new format. Therefore, we’re sending this Intent to Extend OT to allow
> them to check for the possibility of regressions introduced with the
> changes. The features added in the previous OT are listed below. From the
> implementation perspective, there is no difference between the previous OT
> and this time.
>
>
>1.
>
>

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

[Daisuke Enomoto]

Contact emails

hay...@chromium.org, denom...@chromium.org

Explainer

https://github.com/WICG/webpackage/blob/master/explainers/subresource-loading.md

Specification

https://wicg.github.io/webpackage/subresource-loading.html

Design docs

https://chromium.googlesource.com/chromium/src.git/+/refs/heads/master/content/browser/web_package/subresource_loading_origin_trial.md

Summary

We sent the I2S

for the Subresource loading with Web Bundles on April 13th and received a
couple of critical feedback we should address before moving forward. While
we’re actively engaged with various stakeholders to address them, we
realized the previous OT

had expired in M101, which caused an unintended negative impact to the OT
participants in that they couldn’t continue to test their changes to use
the new format. Therefore, we’re sending this Intent to Extend OT to allow
them to check for the possibility of regressions introduced with the
changes. The features added in the previous OT are listed below. From the
implementation perspective, there is no difference between the previous OT
and this time.


   1.

   

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

[Hayato Ito]

Thanks for LGTM.

Regarding https://bit.ly/blink-signals, we've filed a request as follows:

- Gecko: https://github.com/mozilla/standards-positions/issues/590
- WebKit:
https://lists.webkit.org/pipermail/webkit-dev/2021-November/032038.html


On Fri, Nov 5, 2021 at 4:25 AM Daniel Bratell  wrote:

> LGTM to extend the experiment until 101
>
> /Daniel
> On 2021-10-29 10:06, Hayato Ito wrote:
>
> Hi Mike,
>
> Thanks for the comment. We appreciate that. Let me add some clarifications
> and additional info.
>
> On Fri, Oct 29, 2021 at 3:38 AM Mike West  wrote:
>
>> On Thu, Oct 28, 2021 at 6:49 AM Daisuke Enomoto 
>> wrote:
>>
>>> 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_origin_trial.md
>>>
>>> Summary
>>>
>>> Provides a new approach to load a large number of resources efficiently
>>> using a format that allows multiple resources to be bundled, e.g. Web
>>> Bundles.
>>>
>>> Blink component
>>>
>>> Blink>Loader>WebPackaging
>>> 
>>>
>>> TAG review
>>>
>>> https://github.com/w3ctag/design-reviews/issues/616
>>>
>>> (We’ll reopen this once we can have a consensus in the discussion here
>>> )
>>>
>>> TAG review status
>>>
>>> Pending
>>>
>>> Risks
>>> Interoperability and Compatibility
>>>
>>> No interoperability and compatibility risk has been identified for the
>>> prototype phase. This is purely a feature addition for the performance
>>> optimization for now.
>>>
>>> It is expected that a browser which doesn’t support this feature should
>>> load subresources from the network, as usual.
>>>
>>> Gecko: No signal
>>>
>>> WebKit: No signal
>>>
>>> Web developers: No signals
>>>
>>
>> This might be a good time to ask, as per https://bit.ly/blink-signals. :)
>>
>>
>
> That makes sense. Let us do that soon. We'll update this thread when done.
>
>
>
>>
>>> Ergonomics
>>> Activation
>>>
>>> Developers need to package their subresoruces beforehand in order to
>>> take advantage of this feature. We'll work with JS bundler ecosystems to
>>> provide a plugin to package subresources as Web Bundles.
>>>
>>> Security
>>>
>>> No security risk has been identified for the prototype phase.
>>>
>>> Goals for experimentation
>>>
>>> 
>>>
>>> This Intent to Extend includes a few major changes based on the feedback
>>> collected during the original OT, which are 1) 

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

[Daniel Bratell]

LGTM to extend the experiment until 101

/Daniel

On 2021-10-29 10:06, Hayato Ito wrote:

Hi Mike,

Thanks for the comment. We appreciate that. Let me add some 
clarifications and additional info.


On Fri, Oct 29, 2021 at 3:38 AM Mike West  wrote:

On Thu, Oct 28, 2021 at 6:49 AM Daisuke Enomoto
 wrote:


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_origin_trial.md




Summary

Provides a new approach to load a large number of resources
efficiently using a format that allows multiple resources to
be bundled, e.g. Web Bundles.


Blink component

Blink>Loader>WebPackaging




TAG review

https://github.com/w3ctag/design-reviews/issues/616


(We’ll reopen this once we can have a consensus in the
discussion here )


TAG review status

Pending


Risks


Interoperability and Compatibility

No interoperability and compatibility risk has been identified
for the prototype phase. This is purely a feature addition for
the performance optimization for now.


It is expected that a browser which doesn’t support this
feature should load subresources from the network, as usual.

Gecko: No signal

WebKit: No signal

Web developers: No signals


This might be a good time to ask, as per
https://bit.ly/blink-signals. :)


That makes sense. Let us do that soon. We'll update this thread when done.


Ergonomics


Activation

Developers need to package their subresoruces beforehand in
order to take advantage of this feature. We'll work with JS
bundler ecosystems to provide a plugin to package subresources
as Web Bundles.


Security

No security risk has been identified for the prototype phase.


Goals for experimentation



This Intent to Extend includes a few major changes based on
the feedback collected during the original OT, which are 1)

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

[Hayato Ito]

Hi Mike,

Thanks for the comment. We appreciate that. Let me add some clarifications
and additional info.

On Fri, Oct 29, 2021 at 3:38 AM Mike West  wrote:

> On Thu, Oct 28, 2021 at 6:49 AM Daisuke Enomoto 
> wrote:
>
>>
>> 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_origin_trial.md
>>
>> Summary
>>
>> Provides a new approach to load a large number of resources efficiently
>> using a format that allows multiple resources to be bundled, e.g. Web
>> Bundles.
>>
>> Blink component
>>
>> Blink>Loader>WebPackaging
>> 
>>
>> TAG review
>>
>> https://github.com/w3ctag/design-reviews/issues/616
>>
>> (We’ll reopen this once we can have a consensus in the discussion here
>> )
>>
>> TAG review status
>>
>> Pending
>>
>> Risks
>> Interoperability and Compatibility
>>
>> No interoperability and compatibility risk has been identified for the
>> prototype phase. This is purely a feature addition for the performance
>> optimization for now.
>>
>> It is expected that a browser which doesn’t support this feature should
>> load subresources from the network, as usual.
>>
>>
>> Gecko: No signal
>>
>> WebKit: No signal
>>
>> Web developers: No signals
>>
>
> This might be a good time to ask, as per https://bit.ly/blink-signals. :)
>
>

That makes sense. Let us do that soon. We'll update this thread when done.



>
>> Ergonomics
>> Activation
>>
>> Developers need to package their subresoruces beforehand in order to take
>> advantage of this feature. We'll work with JS bundler ecosystems to provide
>> a plugin to package subresources as Web Bundles.
>>
>> Security
>>
>> No security risk has been identified for the prototype phase.
>>
>> Goals for experimentation
>>
>> 
>>
>> This Intent to Extend includes a few major changes based on the feedback
>> collected during the original OT, which are 1) 

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

[Mike West]

On Thu, Oct 28, 2021 at 6:49 AM Daisuke Enomoto 
wrote:

>
> 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_origin_trial.md
>
> Summary
>
> Provides a new approach to load a large number of resources efficiently
> using a format that allows multiple resources to be bundled, e.g. Web
> Bundles.
>
> Blink component
>
> Blink>Loader>WebPackaging
> 
>
> TAG review
>
> https://github.com/w3ctag/design-reviews/issues/616
>
> (We’ll reopen this once we can have a consensus in the discussion here
> )
>
> TAG review status
>
> Pending
>
> Risks
> Interoperability and Compatibility
>
> No interoperability and compatibility risk has been identified for the
> prototype phase. This is purely a feature addition for the performance
> optimization for now.
>
> It is expected that a browser which doesn’t support this feature should
> load subresources from the network, as usual.
>
>
> Gecko: No signal
>
> WebKit: No signal
>
> Web developers: No signals
>

This might be a good time to ask, as per https://bit.ly/blink-signals. :)


>
> Ergonomics
> Activation
>
> Developers need to package their subresoruces beforehand in order to take
> advantage of this feature. We'll work with JS bundler ecosystems to provide
> a plugin to package subresources as Web Bundles.
>
> Security
>
> No security risk has been identified for the prototype phase.
>
> Goals for experimentation
>
> 
>
> This Intent to Extend includes a few major changes based on the feedback
> collected during the original OT, which are 1) 

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

[Daisuke Enomoto]

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_origin_trial.md

Summary

Provides a new approach to load a large number of resources efficiently
using a format that allows multiple resources to be bundled, e.g. Web
Bundles.

Blink component

Blink>Loader>WebPackaging


TAG review

https://github.com/w3ctag/design-reviews/issues/616

(We’ll reopen this once we can have a consensus in the discussion here
)

TAG review status

Pending

Risks
Interoperability and Compatibility

No interoperability and compatibility risk has been identified for the
prototype phase. This is purely a feature addition for the performance
optimization for now.

It is expected that a browser which doesn’t support this feature should
load subresources from the network, as usual.


Gecko: No signal

WebKit: No signal

Web developers: No signals

Ergonomics
Activation

Developers need to package their subresoruces beforehand in order to take
advantage of this feature. We'll work with JS bundler ecosystems to provide
a plugin to package subresources as Web Bundles.

Security

No security risk has been identified for the prototype phase.

Goals for experimentation



This Intent to Extend includes a few major changes based on the feedback
collected during the original OT, which are 1)