Re: [fxtf-drafts] Clarify the feTile area (#327)

I think all of the results for the first example are incorrect.  I've created a fiddle showing what I think the spec says for each step.

http://jsfiddle.net/Lc6v1uyp/

Expected output should be as follows: http://jsfiddle.net/Lc6v1uyp/1/

![capture](https://user-images.githubusercontent.com/840288/49341447-5413de80-f6b2-11e8-8937-4d9331c038bf.PNG)

- Chrome is wrong because the spec says that primitive inputs are clipped by the filter region. However it appears to be scrolling in parts of the feFlood that are outside the filter region.

- Firefox is wrong (I think) because it appears to be using a tiling width and height that is too small.  The spec says that the tile spacing is set by the input subregion.  Firefox appears to be using the clipped 
 6x6 subregion as the tile size instead of the defined 10x10 subregion. 

   The spec says that the input image is hard-clipped, but it isn't explicit about whether that clip affects the primitive subregion bounds.  Chrome obviously doesn't think it does, because it is using the correct (IMO) tiling offsets.

If there is any takeaway from this, it is that the primitive subregion section should be clear about whether or not the subregion bounds are affected by the clip.



-- 
GitHub Notification of comment by BigBadaboom
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/327#issuecomment-443516385 using your GitHub account

Received on Sunday, 2 December 2018 15:33:13 UTC