- From: Nikos Andronikos <Nikos.Andronikos@cisra.canon.com.au>
- Date: Wed, 17 Feb 2016 23:12:56 +0000
- To: Paul LeBeau <paul.lebeau@gmail.com>
- CC: www-svg <www-svg@w3.org>
- Message-ID: <9E50AA02-5B4B-48CF-B659-227F892F3BFE@cisra.canon.com.au>
Hi Paul On 18 Feb 2016, at 6:33 AM, Paul LeBeau <paul.lebeau@gmail.com<mailto:paul.lebeau@gmail.com>> wrote: Hi all I noticed while testing an idea the other day that the fragment identifiers spec is now a little deficient, in that it assumes the other SVG is in an external document. Given that pages containing multiple SVG elements are becoming very common. It might be nice to be able to reference another SVG within the document and supply an SVGViewSpec. An example use case could be: <svg id="main-image" width="1000" height="1000" viewBox="0 0 1000 1000"> ... </svg> <svg id="zoomed-detail"> <use xlink:href="#main_image#svgView(viewBox(100,200,20,20))" width="100" height="100"/> </svg> Thoughts? Would it be useful to extend fragment identiers in some way in order to allow an ID plus an SVGViewSpec etc? Paul That seems like a reasonable use case. We’re currently trailing github for issue tracking, so I’ve copied this there: https://github.com/w3c/svgwg/issues/48 We’ll follow up on github. Thanks, Nikos. The information contained in this email message and any attachments may be confidential and may also be the subject to legal professional privilege. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited. If you have received this email in error, please immediately advise the sender by return email and delete the information from your system.
Received on Wednesday, 17 February 2016 23:13:39 UTC