- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Wed, 23 Jun 2010 20:52:04 +1200
- To: Erik Dahlstrom <ed@opera.com>
- Cc: "www-svg@w3.org" <www-svg@w3.org>
- Message-ID: <AANLkTilLdIGMT0T5zO9E8-mGeyh6brdWrR8G6oKDnVJE@mail.gmail.com>
On Wed, Jun 23, 2010 at 8:11 PM, Erik Dahlstrom <ed@opera.com> wrote: > On Wed, 23 Jun 2010 06:41:16 +0200, Robert O'Callahan < > robert@ocallahan.org> wrote: > > A couple of issues I discovered in the filter spec don't seem to have been >> addressed yet: >> http://lists.w3.org/Archives/Public/www-svg/2008May/0013.html >> > > Now tracked as ISSUE-2334. > Thanks! > > <http://lists.w3.org/Archives/Public/www-svg/2008May/0014.html> >> > > That's a comment on SVG 1.2 filters, and it doesn't seem to apply to SVG > 1.1 Second edition. Oops. I thought I'd removed that from my message. Sorry. > http://lists.w3.org/Archives/Public/www-svg/2008Jun/0007.html >> > > Now tracked as ISSUE-2333. Thanks! > There's also an open issue on the interaction between pointer-events, >> filters, foreignObject, cross-origin IFRAMEs and elementFromPoint: >> http://www.w3.org/Graphics/SVG/WG/track/issues/2071 >> > > As you may see that issue has already been moved to SVG 2.0. It was > believed that it would require substantial changes to the specification, and > as such that it was out of scope for SVG 1.1 second edition. > Ah. I actually don't think that's a good idea. The problem arises in SVG 1.1 and should be solved there, IMHO. The fact that the solution is likely to require a behaviour change somewhere actually makes it more imperative it be solved soon, before the features involved get used more widely. Rob -- "He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6]
Received on Wednesday, 23 June 2010 08:52:31 UTC