Re: [css-masking] clip-path with invalid url

On 12/13/2013 10:49 AM, Tab Atkins Jr. wrote:
> On Thu, Dec 12, 2013 at 2:28 AM, Dirk Schulze <dschulze@adobe.com> wrote:
>> All implementations create a stacking context for clip-path on HTML
> > even if the url() is “invalid”. Means the fragment identifier does
>> not exists, resource is not loaded or does not point to an <clipPath>
>> element. I also tested the behavior on ‘mask’ with the same result.
>>
>> In all cases the three engines WebKit, Gecko and Blink do create a stacking context.
>>
>> Now it is up the implementations if they want to change the behavior.
> Given that all implementations are consistent, I do not expect that
> to happen.
>
> That's the correct behavior anyway - we shouldn't be basing things
> like stacking contexts on used-value time information, which network
> requests qualify as whenever possible.

Ah, yes. I agree. I thought Dirk was saying the opposite, and was
confused...

~fantasai