- From: CJ Ku via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Feb 2017 03:14:14 +0000
- To: public-css-archive@w3.org
CJKu has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-masking] make the behavior of an invalid mask be the same with clip-path and filter == According to css-masking spec,[1]: > A mask reference that is an empty image (zero width or zero height), that fails to download, is not a reference to an mask element, is non-existent, or that cannot be displayed (e.g. because it is not in a supported image format) still counts as an image layer of **transparent black.** Transparent black means the masked object disappeared. The way we handle invalid mask is apparently not the same with clip-path and filter. Both clip-path[2] and filter[3] keep the target element visible. I wonder why only masking has different behavior and think it would be better to keep the consistent. [1] https://drafts.fxtf.org/css-masking-1/#the-mask-image [2] https://drafts.fxtf.org/css-masking-1/#the-clip-path If the URI reference is not valid (e.g it points to an object that doesn’t exist or the object is not a clipPath element), **no clipping is applied**. [3] https://drafts.fxtf.org/filters/#FilterProperty A filter reference to a filter element. For example url(commonfilters.svg#filter). If the filter references a non-existent object or the referenced object is not a filter element, then the whole filter chain is ignored. **No filter is applied to the object**. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/997 using your GitHub account
Received on Thursday, 2 February 2017 03:14:21 UTC