Preparing OT for Viewport Segments and Device Posture.

[Menard, Alexis]

Hi,

 

I’m getting ready to send an intent to experiment with the two APIs in the subject (waiting on few reviews).

 

As a refresher they are APIs targeting foldables and dual screen devices. They will ship everywhere but will only light up on Android and Windows (where you have dual screen and foldable devices).

 

The two APIs are complimentary, they are meant to be used together. The reason they are separate specs for example is mostly history, Microsoft originally incubated the Viewport Segments API and the Device Posture API was originally proposed by Samsung and Intel. Viewport Segments API found its way in the CSS specs and Device Posture API sits in the DAS WG.

 

However, for the origin trial I would like to do a single trial for both APIs so developers will have to only deal with one token. Beside the token, whenever they will play with the APIs it’s important they take into consideration both of them to create enlighten apps for foldables and dual screens.

 

I know it’s not common, but I was told it’s better to discuss it here before I send the intent to blink-dev. Feedback? Anything I should be aware of? Some special care in the OT infrastructure I need to be aware of?

 

Links :

https://chromestatus.com/feature/5185813744975872

https://chromestatus.com/feature/5170498990243840

 

Thanks.

[Domenic Denicola]

This seems reasonable, but will probably cause problems for the tooling. For example, having two Chrome Status entries will make it so that the system wants you to go through the process twice.

Probably it's best to try to consolidate them into one? That might have its own problems, e.g. certain fields that expect only a single URL but you have two. But it seems like those problems will be less painful. And you can use the various text fields, e.g. summary and motivation, to describe the situation.

--
You received this message because you are subscribed to the Google Groups "blink-api-owners-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-api-owners-d...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/DM4PR11MB60683FC3A31079050F98F0D0FA362%40DM4PR11MB6068.namprd11.prod.outlook.com.

[Menard, Alexis]

Hi,

I can definitely consolidate everything in one, but we will also lose information (for e.g. the reviews I went through, Privacy and Security for example) and their comments. How about a meta one instead? Only used for the OT and then we can discard it/archive it. I believe it's ok down the road to send two I2S for each entry to make the tool happy.

When playing around with Chrome Status I can see that I can manually add the Origin Trial details so I could definitively use one of the entries as the main OT entry and populate the second entry manually. But then the only problem is the "View Origin Trial" button which needs to point to the same page on the second entry (the one where the OT was not requested). I'm not sure if someone has the superpower to manually edit this.

I have never run an origin trial myself so I'm throwing random ideas out there.

Thanks.

On Mar 27, 2024, at 1:22 AM, Domenic Denicola <dom...@chromium.org> wrote:



[Mike Taylor]

There is precedent of doing multiple APIs in a single OT, at least with the Privacy Sandbox Ads API OT, which enabled a handful of things (attribution reporting, protected audience, topics, etc).

There was some previous discussion at https://groups.google.com/a/chromium.org/g/blink-dev/c/SD8Ot2gpz4g/m/wa9WRUviAgAJ which recommended a chromestatus entry for the consolidated/meta OT, as well as individual chromestatus entries for each. The meta can then link to the individual chromestatus entries (which can be re-used for I2S).

Let's go for that?

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-api-owners-discuss/057FC480-1BAB-4D34-BFF7-4741B2778A18%40intel.com.

[Menard, Alexis]

Hi,

I'm going to do the meta-approach then.

Thanks.

---

From: Mike Taylor <mike...@chromium.org>
Sent: Wednesday, March 27, 2024 10:40 AM
To: Menard, Alexis <alexis...@intel.com>; Domenic Denicola <dom...@chromium.org>
Cc: blink-api-ow...@chromium.org <blink-api-ow...@chromium.org>
Subject: Re: Preparing OT for Viewport Segments and Device Posture.