W3C home > Mailing lists > Public > public-fxtf-archive@w3.org > June 2017

Re: [fxtf-drafts] [filter-effects] List feMergeNode in the TOC

From: Dirk Schulze via GitHub <sysbot+gh@w3.org>
Date: Sat, 10 Jun 2017 09:46:30 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issue_comment.created-307554677-1497087988-sysbot+gh@w3.org>

I agree that some elements like feMergeNode or the fefunc elements are harder to spot. Should get their dedicated headers.

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

Received on Saturday, 10 June 2017 09:46:36 UTC

This message: [ Message body ]
Next message: Dirk Schulze via GitHub: "Re: [fxtf-drafts] [filter-effects] Why can't opacity() filter function ever increase opacity?"
Previous message: Dirk Schulze via GitHub: "Re: [fxtf-drafts] Inconsistent rules for <title>, <desc> and <metadata>"
In reply to: [ message archived in another list or period ]
Next in thread: Sebastian Zartner via GitHub: "Re: [fxtf-drafts] [filter-effects] List feMergeNode in the TOC"
Maybe reply: Sebastian Zartner via GitHub: "Re: [fxtf-drafts] [filter-effects] List feMergeNode in the TOC"

Mail actions: [ respond to this message ] [ mail a new topic ]
Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]
Help: [ How to use the archives ] [ Search in the archives ]

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:50:21 UTC