Re: [blink-dev] Intent to Ship: Read Chrome device attributes

LGTM3 Please follow up on moving the entire namespace to be behind a managed permission (as Mozilla folks requested ) On Wed, Aug 30, 2023 at 5:40 PM Daniel Bratell wrote: > LGTM2 > > /Daniel > On 2023-08-30

Re: [blink-dev] Intent to Ship: Read Chrome device attributes

LGTM2 /Daniel On 2023-08-30 17:38, Chris Harrelson wrote: LGTM1 On Fri, Aug 11, 2023 at 12:03 PM 'Sergii Bykov' via blink-dev wrote: Hello colleagues, As discussed, I added images to the explainer with examples from ChromeOS of how a managed app and a managed setting look

Re: [blink-dev] Intent to Ship: Read Chrome device attributes

LGTM1 On Fri, Aug 11, 2023 at 12:03 PM 'Sergii Bykov' via blink-dev < blink-dev@chromium.org> wrote: > Hello colleagues, > > As discussed, I added images to the explainer with examples from ChromeOS > of how a managed app and a managed setting look like. > > Sergii > > > On Sat, Jul 29, 2023 at

Re: [blink-dev] Intent to Ship: Read Chrome device attributes

Hello colleagues, As discussed, I added images to the explainer with examples from ChromeOS of how a managed app and a managed setting look like. Sergii On Sat, Jul 29, 2023 at 1:39 AM Reilly Grant wrote: > On Tue, Jul 25, 2023 at 11:57 AM Sergii Bykov wrote: > >> Hello Reilly, colleagues,

Re: [blink-dev] Intent to Ship: Read Chrome device attributes

On Tue, Jul 25, 2023 at 11:57 AM Sergii Bykov wrote: > Hello Reilly, colleagues, > > I replied to #11 in the thread and made a small pull request to the > explainer (directory id promise can also resolve as undefined). > There is still the unresolved question of whether these particular

Re: [blink-dev] Intent to Ship: Read Chrome device attributes

It would definitely help disambiguate the context a bit if that information is provided, but I also sense with policy-based installation and API access gating it does seem to beg the question of whether this can be considered a web platform feature.I am guessing there isn't much appetite from

Re: [blink-dev] Intent to Ship: Read Chrome device attributes

Colleagues, I've addressed #6 earlier today too. Can you please recommend how to proceed with #2 (see prev email)? Sergii On Tue, Jul 25, 2023 at 8:56 PM Sergii Bykov wrote: > Hello Reilly, colleagues, > > I replied to #11 in the thread and made a small pull request to the > explainer

Re: [blink-dev] Intent to Ship: Read Chrome device attributes

Hello Reilly, colleagues, I replied to #11 in the thread and made a small pull request to the explainer (directory id promise can also resolve as undefined). For #6 I will replace 'trusted' applications with 'managed' applications tomorrow. But I'm trying to figure out what to do with the

Re: [blink-dev] Intent to Ship: Read Chrome device attributes

Sergii, thank you for adding some discussion of design alternatives in WICG/WebApiDevice#20 . Please also update the explainer to address the following issues: - WICG/WebApiDevice#1 -

Re: [blink-dev] Intent to Ship: Read Chrome device attributes

On 7/4/23 5:35 AM, 'Sergii Bykov' via blink-dev wrote: Contact emails sby...@google.com Explainer https://github.com/Ananubis/WebApiDevice/blob/master/Explainer.md I see that getAnnotatedAssetId(), getAnnotatedLocation(), getDirectoryId(), and getSerialNumber() are all

[blink-dev] Intent to Ship: Read Chrome device attributes

Contact emailssby...@google.com Explainerhttps://github.com/Ananubis/WebApiDevice/blob/master/Explainer.md Specificationhttps://wicg.github.io/WebApiDevice/device_attributes Summary Device Attributes Web API is a subset of Managed Device Web API, that provides web applications the capability