Re: [blink-dev] Intent to Experiment: Foldable APIs (combo of Device Posture and Viewport Segments APIs)

2024-04-01 Thread Alexis Menard 
Hi,

All requested, all done but one. See in their separate linked Chrome Status
entries.

Thanks.

On Mon, Apr 1, 2024 at 3:51 PM Mike Taylor  wrote:

> One more thing, mind requesting reviews for Privacy, Security,
> Debuggability in your chromestatus entry? Thanks
>
>
> On 4/1/24 3:12 PM, Mike Taylor wrote:
>
> Thanks - sounds good.
>
>
> LGTM to experiment for 4 milestones (125 to 128 inclusive OR 126 to 129
> inclusive).
>
>
> On 4/1/24 2:13 PM, Menard, Alexis wrote:
>
> Hi,
>
> I think 4 milestones would be good (so M125-M129 or M126-M130). It gives
> me ample time to reach out and partner with the various ISVs we have in
> mind.
>
> Thanks.
> --
> *From:* Mike Taylor  
> *Sent:* Monday, April 1, 2024 1:53 PM
> *To:* Menard, Alexis  ;
> blink-dev@chromium.org  
> *Subject:* Re: [blink-dev] Intent to Experiment: Foldable APIs (combo of
> Device Posture and Viewport Segments APIs)
>
>
> How many milestones are you requesting for the OT (whether it starts in
> 125 or 126)?
>
>
> On 4/1/24 1:51 PM, Menard, Alexis wrote:
>
> Contact emails
> alexis.men...@intel.com
>
> Explainer
>
> https://github.com/WICG/visual-viewport/blob/gh-pages/segments-explainer/SEGMENTS-EXPLAINER.md
> https://github.com/w3c/device-posture
>
>
> Specification
> https://www.w3.org/TR/device-posture
> https://www.w3.org/TR/mediaqueries-5/#mf-horizontal-viewport-segments
> https://drafts.csswg.org/css-env-1/#viewport-segments
> https://github.com/w3c/csswg-drafts/pull/9285
>
> Summary
>
> A collection of APIs that help developers target foldable and dual screen
> devices:  Device Posture API and Viewport Segments Enumeration API.
>
> This is an origin trial for both APIs because they are complimentary to
> each other, and we would like developers to use both when they design for
> foldable and dual screen devices. This is mostly a catch up with what
> native APIs on Android already offers for few years. The web APIs are
> available on all OSes however they light up on Android and Windows
> platforms only.
>
> Each have their own chrome status entry :
> https://chromestatus.com/feature/5185813744975872
> https://chromestatus.com/feature/5170498990243840
>
> Demos : https://github.com/foldable-devices/demos
>
> Blink component
> Blink>FoldableAPIs
> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EFoldableAPIs>
>
> TAG review
> Viewport Segments: https://github.com/w3ctag/design-reviews/issues/492 and
> https://github.com/w3ctag/design-reviews/issues/690
> Device Posture : https://github.com/w3ctag/design-reviews/issues/575
>
> TAG review status
> Completed
>
> Risks
>
> Interoperability and Compatibility
>
> None
>
>
> *Gecko*: No signal
> https://github.com/mozilla/standards-positions/issues/882
> https://github.com/mozilla/standards-positions/issues/883
>
>
> *WebKit*: No signal
> https://github.com/WebKit/standards-positions/issues/328
> https://github.com/WebKit/standards-positions/issues/327
>
>
>
> *Web developers*: Positive
>
> *Other signals*:
>
> WebView application risks
>
> *Does this intent deprecate or change behavior of existing APIs, such that
> it has potentially high risk for Android WebView-based applications?*
>
> None
>
>
> Goals for experimentation
> We would like developers to try the two APIs and provide feedback.
>
> Ongoing technical constraints
>
> None
>
> Debuggability
>
> Yes, DevTools support has been added where developers can emulate on
> Android foldable, on Android dual screen and one Windows foldable. In this
> case the APIs are turned on and developers can see how their website react
> on the device (including visualizing the hinge).
>
> Will this feature be supported on all six Blink platforms (Windows, Mac,
> Linux, ChromeOS, Android, and Android WebView)?
> Yes
>
> Is this feature fully tested by web-platform-tests
> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
> ?
> For now, no, we're in the process of adding Web Driver integration.
>
> Flag name on chrome://flags
> Viewport Segments, Device Posture
>
> Finch feature name
> Viewport Segments, Device Posture
>
> Non-finch justification
> None
>
> Requires code in //chrome?
> False
>
> Estimated milestones
>
> M125 if possible, otherwise M126 to start the trial.
>
>
> Link to entry on the Chrome Platform Status
> https://chromestatus.com/feature/5121612962856960?gate=5102929670569984
>
> This intent message was generated by Chrome Platform Status
> <https

Re: [blink-dev] Intent to Experiment: Foldable APIs (combo of Device Posture and Viewport Segments APIs)

2024-04-01 Thread Mike Taylor 
One more thing, mind requesting reviews for Privacy, Security, 
Debuggability in your chromestatus entry? Thanks



On 4/1/24 3:12 PM, Mike Taylor wrote:


Thanks - sounds good.


LGTM to experiment for 4 milestones (125 to 128 inclusive OR 126 to 
129 inclusive).



On 4/1/24 2:13 PM, Menard, Alexis wrote:

Hi,

I think 4 milestones would be good (so M125-M129 or M126-M130). It 
gives me ample time to reach out and partner with the various ISVs we 
have in mind.


Thanks.

*From:* Mike Taylor 
*Sent:* Monday, April 1, 2024 1:53 PM
*To:* Menard, Alexis ; 
blink-dev@chromium.org 
*Subject:* Re: [blink-dev] Intent to Experiment: Foldable APIs (combo 
of Device Posture and Viewport Segments APIs)


How many milestones are you requesting for the OT (whether it starts 
in 125 or 126)?



On 4/1/24 1:51 PM, Menard, Alexis wrote:



Contact emails

alexis.men...@intel.com <mailto:alexis.men...@intel.com>


Explainer

https://github.com/WICG/visual-viewport/blob/gh-pages/segments-explainer/SEGMENTS-EXPLAINER.md 
<https://github.com/WICG/visual-viewport/blob/gh-pages/segments-explainer/SEGMENTS-EXPLAINER.md>
https://github.com/w3c/device-posture 
<https://github.com/w3c/device-posture>



Specification

https://www.w3.org/TR/device-posture 
<https://www.w3.org/TR/device-posture>
https://www.w3.org/TR/mediaqueries-5/#mf-horizontal-viewport-segments 
<https://www.w3.org/TR/mediaqueries-5/#mf-horizontal-viewport-segments>
https://drafts.csswg.org/css-env-1/#viewport-segments 
<https://drafts.csswg.org/css-env-1/#viewport-segments>
https://github.com/w3c/csswg-drafts/pull/9285 
<https://github.com/w3c/csswg-drafts/pull/9285>



Summary

A collection of APIs that help developers target foldable and dual 
screen devices:  Device Posture API and Viewport Segments 
Enumeration API.


This is an origin trial for both APIs because they are complimentary 
to each other, and we would like developers to use both when they 
design for foldable and dual screen devices. This is mostly a catch 
up with what native APIs on Android already offers for few years. 
The web APIs are available on all OSes however they light up on 
Android and Windows platforms only.


Each have their own chrome status entry : 
https://chromestatus.com/feature/5185813744975872 
<https://chromestatus.com/feature/5185813744975872>https://chromestatus.com/feature/5170498990243840 
<https://chromestatus.com/feature/5170498990243840>



Demos : https://github.com/foldable-devices/demos 
<https://github.com/foldable-devices/demos>



Blink component

Blink>FoldableAPIs 
<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EFoldableAPIs>



TAG review

Viewport Segments: 
https://github.com/w3ctag/design-reviews/issues/492 
<https://github.com/w3ctag/design-reviews/issues/492> and 
https://github.com/w3ctag/design-reviews/issues/690 
<https://github.com/w3ctag/design-reviews/issues/690>
Device Posture : https://github.com/w3ctag/design-reviews/issues/575 
<https://github.com/w3ctag/design-reviews/issues/575>



TAG review status

Completed


Risks


Interoperability and Compatibility

None



/Gecko/: No signal
https://github.com/mozilla/standards-positions/issues/882 
<https://github.com/mozilla/standards-positions/issues/882>
https://github.com/mozilla/standards-positions/issues/883 
<https://github.com/mozilla/standards-positions/issues/883>



/WebKit/: No signal
https://github.com/WebKit/standards-positions/issues/328 
<https://github.com/WebKit/standards-positions/issues/328>
https://github.com/WebKit/standards-positions/issues/327 
<https://github.com/WebKit/standards-positions/issues/327>




/Web developers/: Positive

/Other signals/:


WebView application risks

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


None



Goals for experimentation

We would like developers to try the two APIs and provide feedback.


Ongoing technical constraints

None


Debuggability

Yes, DevTools support has been added where developers can emulate on 
Android foldable, on Android dual screen and one Windows foldable. 
In this case the APIs are turned on and developers can see how their 
website react on the device (including visualizing the hinge).



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

Yes


Is this feature fully tested by web-platform-tests

<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?

For now, no, we're in the process of adding Web Driver integration.


Flag name on chrome://fl

Re: [blink-dev] Intent to Experiment: Foldable APIs (combo of Device Posture and Viewport Segments APIs)

2024-04-01 Thread Mike Taylor 

Thanks - sounds good.


LGTM to experiment for 4 milestones (125 to 128 inclusive OR 126 to 129 
inclusive).



On 4/1/24 2:13 PM, Menard, Alexis wrote:

Hi,

I think 4 milestones would be good (so M125-M129 or M126-M130). It 
gives me ample time to reach out and partner with the various ISVs we 
have in mind.


Thanks.

*From:* Mike Taylor 
*Sent:* Monday, April 1, 2024 1:53 PM
*To:* Menard, Alexis ; blink-dev@chromium.org 

*Subject:* Re: [blink-dev] Intent to Experiment: Foldable APIs (combo 
of Device Posture and Viewport Segments APIs)


How many milestones are you requesting for the OT (whether it starts 
in 125 or 126)?



On 4/1/24 1:51 PM, Menard, Alexis wrote:



Contact emails

alexis.men...@intel.com <mailto:alexis.men...@intel.com>


Explainer

https://github.com/WICG/visual-viewport/blob/gh-pages/segments-explainer/SEGMENTS-EXPLAINER.md 
<https://github.com/WICG/visual-viewport/blob/gh-pages/segments-explainer/SEGMENTS-EXPLAINER.md>
https://github.com/w3c/device-posture 
<https://github.com/w3c/device-posture>



Specification

https://www.w3.org/TR/device-posture 
<https://www.w3.org/TR/device-posture>
https://www.w3.org/TR/mediaqueries-5/#mf-horizontal-viewport-segments 
<https://www.w3.org/TR/mediaqueries-5/#mf-horizontal-viewport-segments>
https://drafts.csswg.org/css-env-1/#viewport-segments 
<https://drafts.csswg.org/css-env-1/#viewport-segments>
https://github.com/w3c/csswg-drafts/pull/9285 
<https://github.com/w3c/csswg-drafts/pull/9285>



Summary

A collection of APIs that help developers target foldable and dual 
screen devices:  Device Posture API and Viewport Segments Enumeration 
API.


This is an origin trial for both APIs because they are complimentary 
to each other, and we would like developers to use both when they 
design for foldable and dual screen devices. This is mostly a catch 
up with what native APIs on Android already offers for few years. The 
web APIs are available on all OSes however they light up on Android 
and Windows platforms only.


Each have their own chrome status entry : 
https://chromestatus.com/feature/5185813744975872 
<https://chromestatus.com/feature/5185813744975872>https://chromestatus.com/feature/5170498990243840 
<https://chromestatus.com/feature/5170498990243840>



Demos : https://github.com/foldable-devices/demos 
<https://github.com/foldable-devices/demos>



Blink component

Blink>FoldableAPIs 
<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EFoldableAPIs>



TAG review

Viewport Segments: 
https://github.com/w3ctag/design-reviews/issues/492 
<https://github.com/w3ctag/design-reviews/issues/492> and 
https://github.com/w3ctag/design-reviews/issues/690 
<https://github.com/w3ctag/design-reviews/issues/690>
Device Posture : https://github.com/w3ctag/design-reviews/issues/575 
<https://github.com/w3ctag/design-reviews/issues/575>



TAG review status

Completed


Risks


Interoperability and Compatibility

None



/Gecko/: No signal
https://github.com/mozilla/standards-positions/issues/882 
<https://github.com/mozilla/standards-positions/issues/882>
https://github.com/mozilla/standards-positions/issues/883 
<https://github.com/mozilla/standards-positions/issues/883>



/WebKit/: No signal
https://github.com/WebKit/standards-positions/issues/328 
<https://github.com/WebKit/standards-positions/issues/328>
https://github.com/WebKit/standards-positions/issues/327 
<https://github.com/WebKit/standards-positions/issues/327>




/Web developers/: Positive

/Other signals/:


WebView application risks

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


None



Goals for experimentation

We would like developers to try the two APIs and provide feedback.


Ongoing technical constraints

None


Debuggability

Yes, DevTools support has been added where developers can emulate on 
Android foldable, on Android dual screen and one Windows foldable. In 
this case the APIs are turned on and developers can see how their 
website react on the device (including visualizing the hinge).



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

Yes


Is this feature fully tested by web-platform-tests

<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?

For now, no, we're in the process of adding Web Driver integration.


Flag name on chrome://flags

Viewport Segments, Device Posture


Finch feature name

Viewport Segments, Device Posture


Non-finch justification

None


Requires code i

Re: [blink-dev] Intent to Experiment: Foldable APIs (combo of Device Posture and Viewport Segments APIs)

2024-04-01 Thread Menard, Alexis 
Hi,

I think 4 milestones would be good (so M125-M129 or M126-M130). It gives me 
ample time to reach out and partner with the various ISVs we have in mind.

Thanks.

From: Mike Taylor 
Sent: Monday, April 1, 2024 1:53 PM
To: Menard, Alexis ; blink-dev@chromium.org 

Subject: Re: [blink-dev] Intent to Experiment: Foldable APIs (combo of Device 
Posture and Viewport Segments APIs)


How many milestones are you requesting for the OT (whether it starts in 125 or 
126)?


On 4/1/24 1:51 PM, Menard, Alexis wrote:
Contact emails
alexis.men...@intel.com<mailto:alexis.men...@intel.com>

Explainer
https://github.com/WICG/visual-viewport/blob/gh-pages/segments-explainer/SEGMENTS-EXPLAINER.md
https://github.com/w3c/device-posture


Specification
https://www.w3.org/TR/device-posture
https://www.w3.org/TR/mediaqueries-5/#mf-horizontal-viewport-segments
https://drafts.csswg.org/css-env-1/#viewport-segments
https://github.com/w3c/csswg-drafts/pull/9285

Summary

A collection of APIs that help developers target foldable and dual screen 
devices:  Device Posture API and Viewport Segments Enumeration API.

This is an origin trial for both APIs because they are complimentary to each 
other, and we would like developers to use both when they design for foldable 
and dual screen devices. This is mostly a catch up with what native APIs on 
Android already offers for few years. The web APIs are available on all OSes 
however they light up on Android and Windows platforms only.

Each have their own chrome status entry : 
https://chromestatus.com/feature/5185813744975872 
https://chromestatus.com/feature/5170498990243840

Demos : https://github.com/foldable-devices/demos

Blink component
Blink>FoldableAPIs<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EFoldableAPIs>

TAG review
Viewport Segments: https://github.com/w3ctag/design-reviews/issues/492 and 
https://github.com/w3ctag/design-reviews/issues/690
Device Posture : https://github.com/w3ctag/design-reviews/issues/575

TAG review status
Completed

Risks

Interoperability and Compatibility

None


Gecko: No signal
https://github.com/mozilla/standards-positions/issues/882
https://github.com/mozilla/standards-positions/issues/883


WebKit: No signal
https://github.com/WebKit/standards-positions/issues/328
https://github.com/WebKit/standards-positions/issues/327



Web developers: Positive

Other signals:

WebView application risks

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

None


Goals for experimentation
We would like developers to try the two APIs and provide feedback.

Ongoing technical constraints

None

Debuggability

Yes, DevTools support has been added where developers can emulate on Android 
foldable, on Android dual screen and one Windows foldable. In this case the 
APIs are turned on and developers can see how their website react on the device 
(including visualizing the hinge).

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

Is this feature fully tested by 
web-platform-tests<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?
For now, no, we're in the process of adding Web Driver integration.

Flag name on chrome://flags
Viewport Segments, Device Posture

Finch feature name
Viewport Segments, Device Posture

Non-finch justification
None

Requires code in //chrome?
False

Estimated milestones

M125 if possible, otherwise M126 to start the trial.


Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5121612962856960?gate=5102929670569984

This intent message was generated by Chrome Platform 
Status<https://chromestatus.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<mailto:blink-dev+unsubscr...@chromium.org>.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/DM4PR11MB60684CB86B7D66D2353338C9FA3F2%40DM4PR11MB6068.namprd11.prod.outlook.com<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/DM4PR11MB60684CB86B7D66D2353338C9FA3F2%40DM4PR11MB6068.namprd11.prod.outlook.com?utm_medium=email&utm_source=footer>.

-- 
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/DM4PR11MB606812FD3DB962BAA89E0E76FA3F2%40DM4PR11MB6068.namprd11.prod.outlook.com.

Re: [blink-dev] Intent to Experiment: Foldable APIs (combo of Device Posture and Viewport Segments APIs)

2024-04-01 Thread Mike Taylor 
How many milestones are you requesting for the OT (whether it starts in 
125 or 126)?



On 4/1/24 1:51 PM, Menard, Alexis wrote:



Contact emails

alexis.men...@intel.com 


Explainer

https://github.com/WICG/visual-viewport/blob/gh-pages/segments-explainer/SEGMENTS-EXPLAINER.md 


https://github.com/w3c/device-posture


Specification

https://www.w3.org/TR/device-posture 


https://www.w3.org/TR/mediaqueries-5/#mf-horizontal-viewport-segments
https://drafts.csswg.org/css-env-1/#viewport-segments
https://github.com/w3c/csswg-drafts/pull/9285


Summary

A collection of APIs that help developers target foldable and dual 
screen devices:  Device Posture API and Viewport Segments Enumeration 
API.


This is an origin trial for both APIs because they are complimentary 
to each other, and we would like developers to use both when they 
design for foldable and dual screen devices. This is mostly a catch up 
with what native APIs on Android already offers for few years. The web 
APIs are available on all OSes however they light up on Android and 
Windows platforms only.


Each have their own chrome status entry : 
https://chromestatus.com/feature/5185813744975872 
https://chromestatus.com/feature/5170498990243840 




Demos : https://github.com/foldable-devices/demos


Blink component

Blink>FoldableAPIs 




TAG review

Viewport Segments: https://github.com/w3ctag/design-reviews/issues/492 
 and 
https://github.com/w3ctag/design-reviews/issues/690 

Device Posture : https://github.com/w3ctag/design-reviews/issues/575 




TAG review status

Completed


Risks


Interoperability and Compatibility

None



/Gecko/: No signal
https://github.com/mozilla/standards-positions/issues/882
https://github.com/mozilla/standards-positions/issues/883


/WebKit/: No signal
https://github.com/WebKit/standards-positions/issues/328
https://github.com/WebKit/standards-positions/issues/327



/Web developers/: Positive

/Other signals/:


WebView application risks

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


None



Goals for experimentation

We would like developers to try the two APIs and provide feedback.


Ongoing technical constraints

None


Debuggability

Yes, DevTools support has been added where developers can emulate on 
Android foldable, on Android dual screen and one Windows foldable. In 
this case the APIs are turned on and developers can see how their 
website react on the device (including visualizing the hinge).



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

Yes


Is this feature fully tested by web-platform-tests

?

For now, no, we're in the process of adding Web Driver integration.


Flag name on chrome://flags

Viewport Segments, Device Posture


Finch feature name

Viewport Segments, Device Posture


Non-finch justification

None


Requires code in //chrome?

False


Estimated milestones

M125 if possible, otherwise M126 to start the trial.



Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5121612962856960?gate=5102929670569984 



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/DM4PR11MB60684CB86B7D66D2353338C9FA3F2%40DM4PR11MB6068.namprd11.prod.outlook.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.goo