Proposed Text for Unresolved Resources


In response to an email by Jonathan Chetwynd regarding the behavior of 
unresolved resources, I added proposed wording to the spec for how to 
deal with this [2][3], and tightened up the definition of bounding box 
[4] to say:

"Elements in the rendering tree which reference unresolved resources 
shall still have a bounding box, defined by the position and dimensions 
specified in their attributes, or by the lacuna value for those 
attributes if no values are supplied."

I took the liberty of adding it to the spec, rather than proposing it 
first.  I know this is unorthodox, but I thought it might save us time 
and steps, and also provide context for the additions, which is often 
missing from simple excerpts in email.  Obviously, this still needs to 
be discussed and accepted or rejected, but since we already have the 
ability to back out of changes via CVS, or modify the proposed changes, 
I thought this might streamline things.  If people are not comfortable 
with this method of working, I won't do it anymore.  However, I suggest 
we give it serious consideration.


-Doug Schepers
W3C Team Contact, WebApps, SVG, and CDF

Received on Saturday, 26 July 2008 10:31:14 UTC