Re: ISSUE-2138 (SVG-HTML error processing): Error processing differences in SVG and HTML [Last Call: SVG 1.2 Tiny ]

SVG Working Group Issue Tracker a écrit :
> 
> ISSUE-2138 (SVG-HTML error processing): Error processing differences in SVG and HTML [Last Call: SVG 1.2 Tiny ]
> 
> http://www.w3.org/Graphics/SVG/WG/track/issues/2138
> 
> Raised by: Doug Schepers
> On product: Last Call: SVG 1.2 Tiny 
> 
> Cyril Concolato
> <http://lists.w3.org/Archives/Public/www-svg/2008Oct/0110.html>:
> [[
> * Section 5.9.1 The 'externalResourcesRequired' attribute 
> What is the rationale behind the sentence:
> "If a node enters the error state then the document enters the error state and progressive rendering stops." 
> Is this behavior compatible with traditional HTML processing? 
I've identified the following error states explicitely listed in the spec:
 - playbackOrder='all' and use of discard
 - circular references
 - eRR true but resource not fetched
 - a java class listed in SVG-Handler-Class does not implement EventListenerInitializer2 

My problem is with the 3rd case. For example, if an image (in a group with eRR = true) is not fetched, the UA stops the rest of the rendering of the document. HTML browser don't stop rendering when an image link is broken and this is a more useful behavior. My suggestion is to say that if a node enters the error state (because of an unresolved link), then the UA should inform the user but keep rendering the rest of the document.

Cyril 

-- 
Cyril Concolato
Maître de Conférences/Associate Professor
Groupe Mutimedia/Multimedia Group
Département Traitement du Signal et Images
/Dept. Signal and Image Processing
Ecole Nationale Supérieure des Télécommunications
46 rue Barrault
75 013 Paris, France
http://tsi.enst.fr/~concolat 

Received on Tuesday, 14 October 2008 06:44:07 UTC