On Tue, Jan 5, 2016 at 2:38 PM, Jeff Gilbert <jgilb...@mozilla.com> wrote:
> > Essentially, we would extend the same API but allow the WDTStream > >> interface to apply to more HTML elements, not just HTMLCanvasElement, > >> HTMLImageElement, or HTMLVideoElement. > >> > >> We would also need to implement WEBGL_security_sensitive_resources to > >> enforce the security model: > >> > >> > >> > https://www.khronos.org/registry/webgl/extensions/WEBGL_security_sensitive_resources/ > > > > > > I wish I'd known about this proposal earlier! This looks pretty good, > > though I'd always thought this would be too complicated to spec and > > implement to be practical. Glad to be wrong! Although I think we should > get > > as much feedback as possible on this in case of hidden gotchas. > > Historically in our investigations of this, it seemed very very hard > to guarantee a lack of timing vectors, even just for arithmetic. > (Particularly since we're handing the sources to the driver, which > will try to optimize away as much as it can) > Feedback from GPU vendors would be key here, I think. I'd like to hear that before declaring it dead. If they already did --- RIP :-). Rob -- lbir ye,ea yer.tnietoehr rdn rdsme,anea lurpr edna e hnysnenh hhe uresyf toD selthor stor edna siewaoeodm or v sstvr esBa kbvted,t rdsme,aoreseoouoto o l euetiuruewFa kbn e hnystoivateweh uresyf tulsa rehr rdm or rnea lurpr .a war hsrer holsa rodvted,t nenh hneireseoouot.tniesiewaoeivatewt sstvr esn _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
