Re: [blink-dev] Intent to Ship : HTTP response status code in Resource Timing

2022-10-26 Thread Daniel Bratell

LGTM3

/Daniel

On 2022-10-25 15:29, Mike Taylor wrote:

LGTM2

On 10/25/22 4:39 AM, Mike West wrote:

LGTM1. Thanks for taking feedback around security concerns into account.

-mike


On Mon, Oct 24, 2022 at 4:55 AM Yoav Weiss  
wrote:


Amazing work!! Exciting stuff!

(Recusing myself, as I was somewhat involved)

On Fri, Oct 21, 2022 at 5:37 PM Abin Paul 
wrote:


Contact emails

abin.pa...@gmail.com


Explainer


https://github.com/w3c/resource-timing/blob/gh-pages/Explainers/Response_Status_Code.md


Specification

Resource Timing PR :
https://github.com/w3c/resource-timing/pull/335


Fetch PR : https://github.com/whatwg/fetch/pull/1468


HTML PR :https://github.com/whatwg/html/pull/8405




Summary

Adds a field to PerformanceResourceTiming to indicate the
HTTP response status when the resource was fetched.



Blink component

Blink>PerformanceAPIs>ResourceTiming




TAG review

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



TAG review status

Issues addressed


Risks



Interoperability and Compatibility



Gecko: Positive
(https://github.com/mozilla/standards-positions/issues/665
)


WebKit: No signal
(https://github.com/WebKit/standards-positions/issues/35
)


Web developers:

Developer interest for the feature :
https://github.com/w3c/resource-timing/issues/90



Other signals:


Ergonomics

No



Activation

No risks



Security

No risks



WebView application risks

Does this intent deprecate or change behaviour of existing
APIs, such that it has potentially high risk for Android
WebView-based applications? No



Debuggability

The new attribute shows up in Devtools. No implementation
changes are required.


Will this feature be supported on all six Blink
platforms (Windows, Mac, Linux, Chrome OS, Android,
and Android WebView)?

Yes


Is this feature fully tested by web-platform-tests

?

Yes


https://wpt.fyi/results/resource-timing/response-status-code.html?label=experimental=master




Flag name

#enable-experimental-web-platform-features


Requires code in //chrome?

False


Tracking bug

https://bugs.chromium.org/p/chromium/issues/detail?id=1337256




Non-OSS dependencies

Does the feature depend on any code or APIs outside the
Chromium open source repository and its open-source
dependencies to function?

No


Estimated milestones


Chrome for desktop 109

Chrome for Android 109

Android Webview 109



Anticipated spec changes

No ongoing discussion that could lead to future changes



Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5163838794629120



Links to previous Intent discussions

Intent to prototype:

https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM2ZH3ckNhJ%3DdQmoprkfVU%2Bt5akcUyK9f2%2Bi%3DMRis2TKx63Brg%40mail.gmail.com





This intent message was generated by Chrome Platform Status
.


-- 
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


Re: [blink-dev] Intent to Ship : HTTP response status code in Resource Timing

2022-10-25 Thread Mike Taylor

LGTM2

On 10/25/22 4:39 AM, Mike West wrote:

LGTM1. Thanks for taking feedback around security concerns into account.

-mike


On Mon, Oct 24, 2022 at 4:55 AM Yoav Weiss  wrote:

Amazing work!! Exciting stuff!

(Recusing myself, as I was somewhat involved)

On Fri, Oct 21, 2022 at 5:37 PM Abin Paul 
wrote:


Contact emails

abin.pa...@gmail.com


Explainer


https://github.com/w3c/resource-timing/blob/gh-pages/Explainers/Response_Status_Code.md


Specification

Resource Timing PR :
https://github.com/w3c/resource-timing/pull/335


Fetch PR : https://github.com/whatwg/fetch/pull/1468


HTML PR :https://github.com/whatwg/html/pull/8405




Summary

Adds a field to PerformanceResourceTiming to indicate the HTTP
response status when the resource was fetched.



Blink component

Blink>PerformanceAPIs>ResourceTiming




TAG review

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



TAG review status

Issues addressed


Risks



Interoperability and Compatibility



Gecko: Positive
(https://github.com/mozilla/standards-positions/issues/665
)


WebKit: No signal
(https://github.com/WebKit/standards-positions/issues/35
)


Web developers:

Developer interest for the feature :
https://github.com/w3c/resource-timing/issues/90



Other signals:


Ergonomics

No



Activation

No risks



Security

No risks



WebView application risks

Does this intent deprecate or change behaviour of existing
APIs, such that it has potentially high risk for Android
WebView-based applications? No



Debuggability

The new attribute shows up in Devtools. No implementation
changes are required.


Will this feature be supported on all six Blink
platforms (Windows, Mac, Linux, Chrome OS, Android,
and Android WebView)?

Yes


Is this feature fully tested by web-platform-tests

?

Yes


https://wpt.fyi/results/resource-timing/response-status-code.html?label=experimental=master




Flag name

#enable-experimental-web-platform-features


Requires code in //chrome?

False


Tracking bug

https://bugs.chromium.org/p/chromium/issues/detail?id=1337256




Non-OSS dependencies

Does the feature depend on any code or APIs outside the
Chromium open source repository and its open-source
dependencies to function?

No


Estimated milestones


Chrome for desktop 109

Chrome for Android 109

Android Webview 109



Anticipated spec changes

No ongoing discussion that could lead to future changes



Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5163838794629120



Links to previous Intent discussions

Intent to prototype:

https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM2ZH3ckNhJ%3DdQmoprkfVU%2Bt5akcUyK9f2%2Bi%3DMRis2TKx63Brg%40mail.gmail.com





This intent message was generated by Chrome Platform Status
.


-- 
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


Re: [blink-dev] Intent to Ship : HTTP response status code in Resource Timing

2022-10-25 Thread Mike West
LGTM1. Thanks for taking feedback around security concerns into account.

-mike


On Mon, Oct 24, 2022 at 4:55 AM Yoav Weiss  wrote:

> Amazing work!! Exciting stuff!
>
> (Recusing myself, as I was somewhat involved)
>
> On Fri, Oct 21, 2022 at 5:37 PM Abin Paul  wrote:
>
>> Contact emails
>>
>> abin.pa...@gmail.com
>>
>> Explainer
>>
>>
>> https://github.com/w3c/resource-timing/blob/gh-pages/Explainers/Response_Status_Code.md
>>
>> Specification
>>
>> Resource Timing PR : https://github.com/w3c/resource-timing/pull/335
>>
>> Fetch PR : https://github.com/whatwg/fetch/pull/1468
>>
>> HTML PR :https://github.com/whatwg/html/pull/8405
>>
>>
>> Summary
>>
>> Adds a field to PerformanceResourceTiming to indicate the HTTP response
>> status when the resource was fetched.
>>
>>
>> Blink component
>>
>> Blink>PerformanceAPIs>ResourceTiming
>> 
>>
>> TAG review
>>
>> https://github.com/w3ctag/design-reviews/issues/757
>>
>> TAG review status
>>
>> Issues addressed
>>
>> Risks
>>
>> Interoperability and Compatibility
>>
>> Gecko: Positive (
>> https://github.com/mozilla/standards-positions/issues/665)
>>
>> WebKit: No signal (
>> https://github.com/WebKit/standards-positions/issues/35)
>>
>> Web developers:
>>
>> Developer interest for the feature :
>> https://github.com/w3c/resource-timing/issues/90
>>
>> Other signals:
>>
>> Ergonomics
>>
>> No
>>
>>
>> Activation
>>
>> No risks
>>
>>
>> Security
>>
>> No risks
>>
>>
>> WebView application risks
>>
>> Does this intent deprecate or change behaviour of existing APIs, such
>> that it has potentially high risk for Android WebView-based applications?
>> No
>>
>>
>> Debuggability
>>
>> The new attribute shows up in Devtools. No implementation changes are
>> required.
>>
>> Will this feature be supported on all six Blink platforms (Windows, Mac,
>> Linux, Chrome OS, Android, and Android WebView)?
>>
>> Yes
>>
>> Is this feature fully tested by web-platform-tests
>> 
>> ?
>>
>> Yes
>>
>>
>> https://wpt.fyi/results/resource-timing/response-status-code.html?label=experimental=master
>>
>> Flag name
>>
>> #enable-experimental-web-platform-features
>>
>> Requires code in //chrome?
>>
>> False
>>
>> Tracking bug
>>
>> https://bugs.chromium.org/p/chromium/issues/detail?id=1337256
>>
>>
>> Non-OSS dependencies
>>
>> Does the feature depend on any code or APIs outside the Chromium open
>> source repository and its open-source dependencies to function?
>>
>> No
>>
>> Estimated milestones
>>
>> Chrome for desktop 109
>>
>> Chrome for Android 109
>>
>> Android Webview 109
>>
>>
>> Anticipated spec changes
>>
>> No ongoing discussion that could lead to future changes
>>
>>
>> Link to entry on the Chrome Platform Status
>>
>> https://chromestatus.com/feature/5163838794629120
>>
>> Links to previous Intent discussions
>>
>> Intent to prototype:
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM2ZH3ckNhJ%3DdQmoprkfVU%2Bt5akcUyK9f2%2Bi%3DMRis2TKx63Brg%40mail.gmail.com
>> 
>>
>>
>> This intent message was generated by Chrome Platform Status
>> .
>>
>> --
>> 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
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM2ZH3dDHYs_m262dEUUWLkmSSip8N6AsuuXrVAW92R5xEJ71A%40mail.gmail.com
>> 
>> .
>>
> --
> 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
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfV2YOmnqB1Lui61DqaQRKLfDPDpZvoWZmuJBQeqH_ZYKg%40mail.gmail.com
> 
> .
>

-- 
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 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKXHy%3DfF8Kdn4beRnViyMOCnqPMMHXKja185ysB4_1Qr3GNLsg%40mail.gmail.com.


Re: [blink-dev] Intent to Ship : HTTP response status code in Resource Timing

2022-10-23 Thread Yoav Weiss
Amazing work!! Exciting stuff!

(Recusing myself, as I was somewhat involved)

On Fri, Oct 21, 2022 at 5:37 PM Abin Paul  wrote:

> Contact emails
>
> abin.pa...@gmail.com
>
> Explainer
>
>
> https://github.com/w3c/resource-timing/blob/gh-pages/Explainers/Response_Status_Code.md
>
> Specification
>
> Resource Timing PR : https://github.com/w3c/resource-timing/pull/335
>
> Fetch PR : https://github.com/whatwg/fetch/pull/1468
>
> HTML PR :https://github.com/whatwg/html/pull/8405
>
>
> Summary
>
> Adds a field to PerformanceResourceTiming to indicate the HTTP response
> status when the resource was fetched.
>
>
> Blink component
>
> Blink>PerformanceAPIs>ResourceTiming
> 
>
> TAG review
>
> https://github.com/w3ctag/design-reviews/issues/757
>
> TAG review status
>
> Issues addressed
>
> Risks
>
> Interoperability and Compatibility
>
> Gecko: Positive (https://github.com/mozilla/standards-positions/issues/665
> )
>
> WebKit: No signal (https://github.com/WebKit/standards-positions/issues/35
> )
>
> Web developers:
>
> Developer interest for the feature :
> https://github.com/w3c/resource-timing/issues/90
>
> Other signals:
>
> Ergonomics
>
> No
>
>
> Activation
>
> No risks
>
>
> Security
>
> No risks
>
>
> WebView application risks
>
> Does this intent deprecate or change behaviour of existing APIs, such that
> it has potentially high risk for Android WebView-based applications? No
>
>
> Debuggability
>
> The new attribute shows up in Devtools. No implementation changes are
> required.
>
> Will this feature be supported on all six Blink platforms (Windows, Mac,
> Linux, Chrome OS, Android, and Android WebView)?
>
> Yes
>
> Is this feature fully tested by web-platform-tests
> 
> ?
>
> Yes
>
>
> https://wpt.fyi/results/resource-timing/response-status-code.html?label=experimental=master
>
> Flag name
>
> #enable-experimental-web-platform-features
>
> Requires code in //chrome?
>
> False
>
> Tracking bug
>
> https://bugs.chromium.org/p/chromium/issues/detail?id=1337256
>
>
> Non-OSS dependencies
>
> Does the feature depend on any code or APIs outside the Chromium open
> source repository and its open-source dependencies to function?
>
> No
>
> Estimated milestones
>
> Chrome for desktop 109
>
> Chrome for Android 109
>
> Android Webview 109
>
>
> Anticipated spec changes
>
> No ongoing discussion that could lead to future changes
>
>
> Link to entry on the Chrome Platform Status
>
> https://chromestatus.com/feature/5163838794629120
>
> Links to previous Intent discussions
>
> Intent to prototype:
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM2ZH3ckNhJ%3DdQmoprkfVU%2Bt5akcUyK9f2%2Bi%3DMRis2TKx63Brg%40mail.gmail.com
> 
>
>
> This intent message was generated by Chrome Platform Status
> .
>
> --
> 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
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM2ZH3dDHYs_m262dEUUWLkmSSip8N6AsuuXrVAW92R5xEJ71A%40mail.gmail.com
> 
> .
>

-- 
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 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfV2YOmnqB1Lui61DqaQRKLfDPDpZvoWZmuJBQeqH_ZYKg%40mail.gmail.com.


[blink-dev] Intent to Ship : HTTP response status code in Resource Timing

2022-10-21 Thread Abin Paul
Contact emails

abin.pa...@gmail.com

Explainer

https://github.com/w3c/resource-timing/blob/gh-pages/Explainers/Response_Status_Code.md

Specification

Resource Timing PR : https://github.com/w3c/resource-timing/pull/335

Fetch PR : https://github.com/whatwg/fetch/pull/1468

HTML PR :https://github.com/whatwg/html/pull/8405


Summary

Adds a field to PerformanceResourceTiming to indicate the HTTP response
status when the resource was fetched.


Blink component

Blink>PerformanceAPIs>ResourceTiming


TAG review

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

TAG review status

Issues addressed

Risks

Interoperability and Compatibility

Gecko: Positive (https://github.com/mozilla/standards-positions/issues/665)

WebKit: No signal (https://github.com/WebKit/standards-positions/issues/35)

Web developers:

Developer interest for the feature :
https://github.com/w3c/resource-timing/issues/90

Other signals:

Ergonomics

No


Activation

No risks


Security

No risks


WebView application risks

Does this intent deprecate or change behaviour of existing APIs, such that
it has potentially high risk for Android WebView-based applications? No


Debuggability

The new attribute shows up in Devtools. No implementation changes are
required.

Will this feature be supported on all six Blink platforms (Windows, Mac,
Linux, Chrome OS, Android, and Android WebView)?

Yes

Is this feature fully tested by web-platform-tests

?

Yes

https://wpt.fyi/results/resource-timing/response-status-code.html?label=experimental=master

Flag name

#enable-experimental-web-platform-features

Requires code in //chrome?

False

Tracking bug

https://bugs.chromium.org/p/chromium/issues/detail?id=1337256


Non-OSS dependencies

Does the feature depend on any code or APIs outside the Chromium open
source repository and its open-source dependencies to function?

No

Estimated milestones

Chrome for desktop 109

Chrome for Android 109

Android Webview 109


Anticipated spec changes

No ongoing discussion that could lead to future changes


Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5163838794629120

Links to previous Intent discussions

Intent to prototype:
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM2ZH3ckNhJ%3DdQmoprkfVU%2Bt5akcUyK9f2%2Bi%3DMRis2TKx63Brg%40mail.gmail.com



This intent message was generated by Chrome Platform Status
.

-- 
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 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM2ZH3dDHYs_m262dEUUWLkmSSip8N6AsuuXrVAW92R5xEJ71A%40mail.gmail.com.