- From: Chris Lilley <chris@w3.org>
- Date: Tue, 8 Feb 2011 11:25:59 +0100
- To: Cameron McCormack <cam@mcc.id.au>
- CC: public-svg-wg@w3.org
On Tuesday, February 8, 2011, 2:40:04 AM, Cameron wrote: CM> Hi Chris. CM> Chris Lilley: >> linking-a-07-t.svg assumes that the viewer can create new frames. For >> a viewer which runs fullscreen on a device, or which uses a single >> window, it is not clear from the SVG spec that suc viewers are non >> conformant. A new window/tab/frame should be created if the viewer >> does multiple windows/tabs/frames. If it doesn't, (and thus displays >> the content in the same window) should the result be a fail or not? CM> Perhaps there should be distinct conformance classes for implementations CM> that do and do not support new windows/tabs? That is a possibility. CM> We could have Conforming CM> Dynamic SVG Viewers (currently the highest one) not require CM> xlink:show="" to do anything special, while Conforming Multi-Window CM> Dynamic SVG Viewers would. Is it @xlink:show or is it @target? I would have thought the latter. CM> Is that too big of a change to make at this point? That is certainly a concern. And it might be that the Multi-Window class would have additional requirements on it as well (making it effectively the SVG-in-HTML class?) The conservative, minimal change for a second edition would be to clarify that Dynamic SVG Viewers are not required to handle multiple independent viewports, deferring the larger conformance class for SVG 2. But that would be a shame as we have 4 passes on linking-a-07 already, while such a change would make that test non-normative. So my suggestion would be to leave it as is for now, and raise an issue on multi window/tab/frame for SVG2. -- Chris Lilley Technical Director, Interaction Domain W3C Graphics Activity Lead, Fonts Activity Lead Co-Chair, W3C Hypertext CG Member, CSS, WebFonts, SVG Working Groups
Received on Tuesday, 8 February 2011 10:26:01 UTC