- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Sep 2016 05:35:46 +0000
- To: public-svg-issues@w3.org
In case there are more children than the defined number of inputs allowed, the excessive child elements would be ignored. But you're right, there is no indication how many elements they take. The inconsistency of filters like `<feMerge>`, which already allow child filter elements, is another reason to allow them for all filters. But yes, allowing to add the filter elements directly to `<feMerge>` instead of having to use the indirection of `<feMergeNode>` would be great. > This also doesn't allow for branching / re-joining filter structures, so you'd still need the attribute naming option for that. Yes, this and backwards compatibility are the reasons why they need to be kept. > But it's definitely a topic worth discussing. I can leave this issue open here for that, but if it eventually narrows to a specific proposal the FXTF repo is the place for the feature request, since it's a shared spec now. Ah right, sorry for that. I just thought that it only affects the SVG part of the module, so I should file the issue here. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/svgwg/issues/258#issuecomment-246253863 using your GitHub account
Received on Monday, 12 September 2016 05:35:53 UTC