Re: [w3c/manifest] Add optional `translations` member (#676)

> Reporting API is also used for reporting issues around storage today (we recently had a TAG review for that) and it was designed in a way that it is supposed to be generic and not just for high profile security issues :-)

With multi implementer support or was it a WICG proposal from one vendor? 

Again, from experience, the more we try to stack features/capabilities, the least likely any of this gets implemented. I'm not saying these are not good ideas. I just know that if we stack a whole bunch of stuff, it's less likely to get implemented (or will just be another single engine thing). 


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/676#issuecomment-818576183

Received on Tuesday, 13 April 2021 09:04:27 UTC