The privacy and security teams review all intents, so requesting reviews
and answering the relevant questionnaires is the best path forward.
Looking forward to the new I2S - thanks!
On 3/14/24 11:22 AM, Zheda Chen wrote:
More details are updated in ChromeStatus, including interoperability
and compatibility risks, Safari/Firefox views, web platform tests. It
compares the behaviors across different browser vendors.
https://chromestatus.com/feature/5106220399853568
Will send the updated "intent to ship" to this thread later if it
looks good.
AFAIK, I don't see potential privacy/security issues, so can i set
"security review status" and "privacy review status" to "not
applicable"? Please let us know if you have any concerns.
On Wednesday, March 13, 2024 at 10:00:35 AM UTC+8 dom...@chromium.org
wrote:
Can you fill out the interoperability and compatibility risks
section here? I don't think standards position requests are
necessary, but saying how this behavior might break existing sites
that assume Chromium's current behavior, and how this new behavior
compares to WebKit and Gecko, would be helpful.
Also, can you request the
privacy/security/enterprise/debuggability/testing gates on Chrome
Status?
On Tue, Mar 12, 2024 at 10:12 PM Zheda Chen <zheda...@intel.com>
wrote:
Okay I update the process stage in Chrome Platform Status, and
paste the newly-generated Intent above. Please take a look.
https://chromestatus.com/feature/5106220399853568
--
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/70b96db6-f908-48dc-82b8-a68eab3cce60%40chromium.org.
