I'm not too familiar with the "intent to ship" process for mozilla [1] Given that no one objected to my proposal, can I submit a patch to remove the runtime flag and put it up for review?
1: https://wiki.mozilla.org/WebAPI/ExposureGuidelines On Tue, Mar 25, 2014 at 11:11 AM, Rik Cabanier <caban...@gmail.com> wrote: > > > > On Tue, Mar 25, 2014 at 9:43 AM, Anne van Kesteren <ann...@annevk.nl>wrote: > >> On Tue, Mar 25, 2014 at 4:22 PM, Rik Cabanier <caban...@gmail.com> wrote: >> > The one shipping implementation was Safari and it was implemented last >> year >> > by Dirk. He renamed it last week to Path2D. >> >> I see, if it has been in Safari for over a year as Path, the claims it >> causes compatibility issues seem somewhat overblown? > > > We did find a couple of paper.js websites that were broken by that change. > > >> It just seems >> weird to name this interface differently from the others. I guess it >> does not matter much... >> > > yes, some people felt strongly that it should not be so generic and others > didn't have a strong opinion. > > I posted a small example that shows the Path2D object in action: > http://cabanier.github.io/canvg/convert.html > It will work in any browser, but to get the best performance, you need to > install the latest nightly and turn "canvas.path" on in "about:config". > > The test redraws the SVG in a loop. Without Path2D support, the test takes > up 14% of my CPU but with support turned on, it drops down to 5% > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
