W3C home > Mailing lists > Public > www-svg@w3.org > March 2010

Assitance with potential spec ambiguities

From: Patrick Dengler <patd@microsoft.com>
Date: Tue, 23 Mar 2010 16:53:49 +0000
To: "www-svg@w3.org" <www-svg@w3.org>
Message-ID: <4A2DB3AE4504E944AF122BBFBA7FBA1F4E7A0BE1@TK5EX14MBXC112.redmond.corp.microsoft.com>
I am happy to address these in email or on our teleconference.  As always, please forgive me if these have been already addressed. I do look at the issue tracker and updates to 1.1 2nd edition.

SVGException SVG_INVALID_VALUE_ERR details
=====================================

In the code below:

    l = document.getElementById("svg").preserveAspectRatio.baseVal.align;
    alert(l);
    try
    {
    document.getElementById("svg").preserveAspectRatio.baseVal.align = -1;
    }
    catch(e)
    {
    alert("exception:" + e);
    }
    l = document.getElementById("svg").preserveAspectRatio.baseVal.align;
    alert(l);

   Opera/Chrome - no exception, second output = 65535
   FF3.6 - Throws an exception, second output = 6  (correct in the page context)

Essentially the spec is implying that this exception should be thrown in cases like this - although the exception is listed explicitly in the spec in only a few places (e.g. SVGColor).  

For the case above
1. Should the browser throw an exception in this particular instance? (on setting this invalid value)
2. Should the browser set the value to SVG_PRESERVEASPECTRATIO_UNKNOWN or keep the value attempted to be set.
3. Should the browser throw an exception in all cases when attempting to set an invalid value? (anywhere an invalid value is set which lacks a more specific exception code) and should that exception be SVG_INVALID_VALUE_ERR?
Received on Tuesday, 23 March 2010 16:54:24 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:44 GMT