Hi, We are about to start testing the API for a suite of kiosks being deployed to a chain of restaurants in the UK.
I am currently working remotely so do not have physical access to the Chrome OS devices we are testing on. I have registered the domain on Chrome Origin Trials but when I try to use the API on the test machines I get the following error... *The current origin cannot use this web API because it is not allowed by the DeviceAttributesAllowedForOrigins policy."* Do I need physical access to the devices to configure support for the new API? On Thursday, 22 July 2021 at 23:36:12 UTC+1 [email protected] wrote: > That's a good justification. LGTM. > > On Thursday, July 22, 2021 at 2:08:15 PM UTC-7 Anqing Zhao wrote: > >> Thanks Chris & Manuel. I have replied to the TAG, and filled in 'goals >> for experiments'. Let me copy-paste the goals here as well. Any suggestion >> or question is welcome :) >> >> Experiment GoalsWe want to collect feedback for the new device >>> attributes web APIs via this experiment. One main goal is to make sure the >>> current API design and functionalities can fulfill web developers’ actual >>> requirements, especially those enterprise developers who expressed interest >>> in the ‘initial proposal’ thread ( >>> https://github.com/WICG/proposals/issues/14). In particular, we want to >>> double check whether the current permission model / flow can meet >>> enterprise security and privacy requirements, and integrate well with their >>> products before shipping. >> >> >> TBH, whether we are able to ship this API *soon* really depends on what >> (how many) feedbacks will be received during the origin-trial period. Yeah, >> many thanks for the links. Let me try to fill them both according to the >> guides :) >> >> On Thu, Jul 22, 2021 at 9:44 PM Manuel Rego <[email protected]> wrote: >> >>> >>> On Friday, 16 July 2021 at 15:39:36 UTC+2 Anqing Zhao wrote: >>> >>>> TAG review >>>> https://github.com/w3ctag/design-reviews/issues/606 >>>> >>>> TAG review statusPending >>>> >>> >>> The TAG seems to be waiting for your answers on that issue. It'd be nice >>> to provide some feedback about the status of things. >>> >>> >>>> Interoperability and Compatibility >>>> >>>> >>>> Gecko: No signal >>>> >>>> WebKit: No signal >>>> >>>> Web developers: No signals >>>> >>> >>> BTW, if we're planning to ship soon, it doesn't harm to fill requests >>> for signals. See https://bit.ly/blink-signals & >>> https://goo.gle/developer-signals. >>> >>> Cheers, >>> Rego >>> >>> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/35a5cf97-f86a-4710-a79d-5c53f779543dn%40chromium.org.
