This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 5594 - processing invalid external URI references
Summary: processing invalid external URI references
Status: NEW
Alias: None
Product: SVG
Classification: Unclassified
Component: Document Structure (show other bugs)
Version: SVG 1.2 Tiny
Hardware: Macintosh All
: P2 normal
Target Milestone: Test Suite
Assignee: Doug Schepers
QA Contact: SVG Public List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-28 10:31 UTC by j.chetwynd
Modified: 2008-03-28 10:31 UTC (History)
0 users

See Also:

Attachments

Description j.chetwynd 2008-03-28 10:31:22 UTC 
what is the required (or desirable behaviour) when processing a  
document with an invalid external URI reference, for instance in a  
<use> or perhaps <image> element?

when externalResourcesRequired is undefined or "false"
http://www.w3.org/TR/SVGMobile12/struct.html#ExternalResourcesRequiredAttribute

The author and user might both generally be expected to wish to be advised.
e.g. missing images in HTML are generally indicated by a symbol.

iirc recent versions of Opera and Amaya ignored the 'missing' content, whereas batik did not render any of the document and produced an error dialogue.