- From: Marcos Caceres <marcosc@w3.org>
- Date: Fri, 20 Aug 2021 18:11:55 +1000
- To: Yoav Weiss <yoavweiss@google.com>
- Cc: Thomas Steiner <tomac@google.com>, "Christiansen, Kenneth R" <kenneth.r.christiansen@intel.com>, "Kostiainen, Anssi" <anssi.kostiainen@intel.com>, Addy Osmani <addyo@google.com>, "TOREINI, EHSAN" <ehsan.toreini@durham.ac.uk>, Noam Helfman <noamh@microsoft.com>, Tarun Bansal <tbansal@google.com>, W3C Devices and Sensors WG <public-device-apis@w3.org>, Alex Russell <slightlyoff@chromium.org>, "ilya@igvita.com" <ilya@igvita.com>, Pete LePage <petele@google.com>
> On 20 Aug 2021, at 5:31 pm, Yoav Weiss <yoavweiss@google.com> wrote: > > OK, that sounds perfectly reasonable. It also feels extremely similar to what Thomas is proposing % the spec & interface name. Would renaming those help from your perspective? It's not a matter of renaming, it's a matter of nailing down the limited set of use cases. What I'd really like to see is Gecko and WebKit folks, together with the dev community/sites that need this, be like: "yep, X, Y, and maybe Z would be great things to figure out together." Personally, what I'd like to see is ~3-5 different ways of attempting to solve those cases (e.g., here is solution X with an API, here is one with declarative <whatever> element or attribute, and so on...). That way, we don't become overly attached to a single solution. If folks can spare a few minutes, Ilya has a great post + talk "retrospective at performance.now()", which I think is super relevant here (~20min mark) - around considering approaching these kinds of problems from different perspectives: https://discourse.wicg.io/t/proposal-native-media-optimization-and-basic-editing-support/4068/12
Received on Friday, 20 August 2021 08:12:13 UTC