W3C home > Mailing lists > Public > www-svg@w3.org > January 2016

Re: SVG pathSegList Deprecated via Chrome's version 48 TODAY!

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 25 Jan 2016 10:49:51 -0800
Message-ID: <CAAWBYDANUkppfaDYU-nsWZ9DbqzTpR9TjMYZh4SgX5VKNYjzxA@mail.gmail.com>
To: Francis Hemsher <fhemsher@gmail.com>
Cc: www-svg <www-svg@w3.org>
On Sun, Jan 24, 2016 at 2:32 PM, Francis Hemsher <fhemsher@gmail.com> wrote:
> Initially it was somewhat of a challenge 15 years ago to wrap my head around
> building SVG paths via pathSegList  and its methods. I persevered, and
> thereby have about 200 files within various apps online that use this
> feature.
>
> I believe Google has seriously jumped the gun in dumping this feature with
> no warning to developers. It will take quite a few hours/days/weeks to fix
> my pages to run in Chrome. In the meantime about 50% of my users will crash
> when getting into the SVG path.
>
> I'm hoping for a bit of feedback to the Chrome folks to reconsider this, and
> a rollback to support of SVG's pathSegList. HELP!
> See the following:
>  https://code.google.com/p/chromium/issues/detail?id=539385
> https://code.google.com/p/chromium/issues/detail?id=568735

Sending email to blink-dev@chromium.org is the most effective way to
communicate with Chrome devs.

~TJ
Received on Monday, 25 January 2016 18:50:37 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:43 UTC