- From: Mark Birbeck <mark.birbeck@x-port.net>
- Date: Thu, 26 May 2005 10:58:58 +0100
- To: "'MAHE Vincent RD-TECH-REN'" <v.mahe@francetelecom.com>, "'Jon Ferraiolo'" <jon.ferraiolo@adobe.com>, "'Ola Andersson'" <Ola.Andersson@ikivo.com>
- Cc: "'KONO Masahiko'" <kono.masahiko@canon.co.jp>, <www-svg@w3.org>
Hi Vincent, > Since everybody seems to agree on this, has Ola been given an action to update the > Tiny spec. accordingly so that it becomes clearer for every developer & implementer > which reads the spec. ? I know we now agree on the problem, but I don't agree that the solution is some sort of 'clarification' in SVG Tiny. If the problem really is there, then DOM 3 Events needs to be corrected. I say "if", because it may be that there is an aspect of the implementation that the authors haven't explained that makes this problem go away. But my experience of trying to implement this last year was that it was not possible to make DOM 3 Events and DOM 2 Events co-exist. There are a couple of ways that this might be solved, but I assume that discussion should take place on a different forum. Regards, Mark Mark Birbeck CEO x-port.net Ltd. e: Mark.Birbeck@x-port.net t: +44 (0) 20 7689 9232 w: http://www.formsPlayer.com/ b: http://internet-apps.blogspot.com/ Download our XForms processor from http://www.formsPlayer.com/
Received on Thursday, 26 May 2005 09:59:28 UTC