> > When looking at the API, I found that it's unclear why a cropID is needed > (compared to using an element ID instead, or just passing the element to > `cropTo`). Would be good to further explain that. >
Will do along with my next pass over the spec and README, which I intend to do after we're done coding the MVP. May be good to try and move the spec over to the WICG. I saw activity on > the related proposal <https://github.com/WICG/proposals/issues/39>, so it > may be good to get explicit support from folks that'd enable such a move. > I am scheduled to present about this feature on the WebRTC Working Group interim in November. After that, and after we have the MVP landed, I intend to step up my partner-seeking efforts. > Plans to file for a TAG review? > Definitely, but I want to have a first do a first pass in the WebRTC Working Group and have the MVP landed and exposed to OT. Can you file for https://bit.ly/blink-signals? > I intend to do so after I've had time to present to Apple and Mozilla in the aforementioned interim. -- 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/a0a6e5e6-4277-40ac-b982-53dbb4a2e3b7n%40chromium.org.
