Re: [svgwg] What should happen regarding 1.2 Tiny features that are not mentioned in SVG2 spec?

Tiny 1.2 is mostly being treated as a dead-end fork of SVG.  So 
consider all of those as deprecated or obsolete.

>From what I can tell, most of the references to Tiny in SVG 2 are in 
the form of annotations about specific features from that spec that we
 decided to keep.

However, there are a couple back-references to Tiny in the 
`vector-effects` section and the "Painting vector effects" sections. 
Probably both need a re-write.  (There's also links to Tiny in the 
definitions-filters.xml file that we need to update to point to 
equivalent definitions in SVG 2.  )

Beyond that: If there are specific features from Tiny you want to 
preserve in SVG 2, that could be considered as a feature request.  
>From your list, I can say that some are now redundant:

- `viewport-fill` is replaced with CSS `background` properties 
- `buffered-rendering` was dropped in favor of `will-change`
- the multi-line text model has been completely over-hauled so that 
`<textArea>` is not required

However, a `<tbreak>` element may still prove useful in the future, as
 could a `editable` option.  

A `ref` type transform, that could reset some or all of the 
transformation sequence to another SVG, is definitely something I'd be
 interested in, but it would have to be discussed in the context of 
the CSS Transforms Level 2 module.

-- 
GitHub Notification of comment by AmeliaBR
Please view or discuss this issue at 
https://github.com/w3c/svgwg/issues/199#issuecomment-231842682 using 
your GitHub account

Received on Monday, 11 July 2016 19:43:58 UTC