Re: [compositing-1] please move non-separable effects to Level 2

On Sat, Apr 19, 2014 at 12:34 PM, Rik Cabanier <cabanier@gmail.com> wrote:

> On Fri, Apr 18, 2014 at 4:23 PM, Robert O'Callahan <robert@ocallahan.org>wrote:
>
>> I object on the grounds that the justifications presented so far seem
>> inadequate to me.
>>
>
> What would be an adequate justification?
>

-- "These modes have no use cases."
-- "These modes cannot be efficiently implemented on any existing platform."
-- "The behavior of these modes is not fully specified."
-- "No browser vendor plans to support these modes."

If a browser vendor can't support a certain feature, isn't that good enough?
>

"Browser X can't support a feature" is a very ambiguous phrase so I can't
really answer that question.

In this case, AFAIK Webkit isn't implementing these modes because iOS/OSX
APIs currently don't allow them to be implemented the way the Webkit team
would like to implement them. That is an implementation issue internal to
Apple that apparently can and will be resolved via future software changes.
I.e. the issue is both temporary and unique to Webkit.

So an accurate phrasing of your question would be, "If a single browser
vendor isn't yet able to ship support for a feature, but plans to, should
we remove it from the spec?" I feel confident the answer is no.

Rob
-- 
Jtehsauts  tshaei dS,o n" Wohfy  Mdaon  yhoaus  eanuttehrotraiitny  eovni
le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o  Whhei csha iids  teoa
stiheer :p atroa lsyazye,d  'mYaonu,r  "sGients  uapr,e  tfaokreg iyvoeunr,
'm aotr  atnod  sgaoy ,h o'mGee.t"  uTph eann dt hwea lmka'n?  gBoutt  uIp
waanndt  wyeonut  thoo mken.o w