[svgwg] Issue: Since vector - effect options other than non - scaling - stroke already have multiple implementations, is the "at risk" flag valid? marked as Entire spec from Satoru Takagi via GitHub on 2017-02-17 (public-svg-issues@w3.org from February 2017)

From: Satoru Takagi via GitHub <sysbot+gh@w3.org>
Date: Fri, 17 Feb 2017 01:24:30 +0000
To: public-svg-issues@w3.org
Message-ID: <issues.labeled-208303736-None-sysbot+gh@w3.org>

satakagi has just labeled an issue for https://github.com/w3c/svgwg as
 "Entire spec":

== Since vector - effect options other than non - scaling - stroke 
already have multiple implementations, is the "at risk" flag valid? ==
Gecko patch: https://bugzilla.mozilla.org/show_bug.cgi?id=1318208
Polyfill: 
http://svg2.mbsrv.net/devinfo/devstd/non-scaling-objects-2/VectorEffect_polyfill_wScreen.html


See https://github.com/w3c/svgwg/issues/306

Received on Friday, 17 February 2017 01:24:37 UTC