Re: Suggestion: Future SVG Updates

Hi, Francis–

Yes, that's most likely the course that SVG2 and future versions will 
take. SVG2 will probably be reduced to those features that are already 
implemented (or have clear browser implementation plans), and everything 
else will be deferred to future SVG modules which are focused 
specifically on a particular feature.


On 10/14/16 8:37 AM, Francis Hemsher wrote:
> Hi All,
> Browser updates for the SVG 2 will most likely to be to adopt various
> new features individually rather than the complete package.
> The method for current browser updates no longer takes the 'Candidate
> Recommendation'  approach; they are always updating as required.
> Therefore why shouldn't SVG do this?
> It seems to me that building and formalizing individual new features in
> SVG would be in keeping with the browser's update methods. Also, we, the
> developers, wouldn't have to wait 5 years hence to apply them.
> Regards,
> Francis Hemsher

Received on Friday, 14 October 2016 18:15:28 UTC