Re: [svgwg] dur attribute should permit leading .

The Working Group just discussed `out of range value on an enum in the DOM`.

<details><summary>The full IRC log of that discussion</summary>
&lt;krit> topic: out of range value on an enum in the DOM<br>
&lt;liam> github issue: https://github.com/w3c/svgwg/issues/423<br>
&lt;krit> krit: this seems to be on svgDOM<br>
&lt;krit> liam: seems a mix of browsers do the one thing and other browsers another thin g<br>
&lt;krit> krit: all tested browsers throw (Edge not tested)<br>
&lt;krit> krit: just that they throw differently<br>
&lt;krit> krit: according to the comment, Edge throws but does set baseVal to something else<br>
&lt;krit> krit: first question should be throw or not to throw<br>
&lt;krit> chris: I think we should keep baseVal unchanged which means throw<br>
&lt;krit> chris: 1. most implementations do it 2. it is more useful<br>
&lt;krit> AmeliaBR: silently failing is what CSS does.<br>
&lt;krit> AmeliaBR: we should not set the value on invalid value. Shall we throw or be silent about it.<br>
&lt;krit> resolution: not change current baseVal on setting it to an out-of-range value<br>
&lt;krit> resolution: Throw on out-of-range value for baseValue<br>
&lt;liam> https://wpt.fyi/results/svg/types/scripted/SVGAnimatedEnumeration-SVGClipPathElement.html has results for safari &amp; firefox<br>
&lt;liam> ff - SyntaxError: An invalid or illegal string was specified<br>
&lt;krit> krit: Open question: What should we throw. Put this part back to GitHub?<br>
&lt;liam> safari - SVG_INVALID_VALUE_ERR<br>
&lt;liam> chrome - TypeError<br>
&lt;krit> krit: I'd be in favour for TypeError<br>
&lt;krit> liam: invalid value or TypeError might make sense.<br>
&lt;krit> AmeliaBR: TypeError would be more in line with what we spec. But depends on how difficult it is for browser<br>
&lt;krit> resolution: Use TypeError and wait for UA implementation feedback<br>
&lt;krit> s/Use TypeError/Use TypeError for out-of-range values on baseVal/<br>
&lt;liam> github issue: https://github.com/w3c/svgwg/issues/394<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/svgwg/issues/394#issuecomment-396354748 using your GitHub account

Received on Monday, 11 June 2018 19:15:30 UTC