Image: Use the constrainable pattern instead of creating a subtly different function set

It may have gotten lost in the flurry of issues raised yesterday, but
this one is where I think the WG needs to have input.

The question has Giri and me on opposite sides of the issue; we need
more people to chime in.

I've been assured that both approaches are implementable.

Harald


Den 07. des. 2016 13:21, skrev Harald Alvestrand via GitHub:
> alvestrand has just created a new issue for 
> https://github.com/w3c/mediacapture-image:
> 
> == Use the constrainable pattern instead of creating a subtly 
> different function set ==
> The combination of getPhotoCapabilities (with both ranges and current 
> settings) and setOptions creates an almost equivalent set of 
> functionalities to the constrainable pattern used on MediaStreamTrack.
> 
> Two nearly identical patterns is a bad thing for the platform. Please 
> reconsider.
> 
> (This has been discussed before, and I know giri does not agree with 
> me. I wish for the discussion to be recorded as a top-level issue in 
> this tracker.)
> 
> 
> Please view or discuss this issue at 
> https://github.com/w3c/mediacapture-image/issues/124 using your GitHub
>  account
>

Received on Thursday, 8 December 2016 15:02:19 UTC