W3C home > Mailing lists > Public > www-svg@w3.org > May 2011

Re: agenda+ SVG 2 Features and Approach

From: Robert O'Callahan <robert@ocallahan.org>
Date: Tue, 10 May 2011 22:07:18 +1200
Message-ID: <BANLkTikWBKdaHGxOy7WJkNvdNiugcRYhKQ@mail.gmail.com>
To: Doug Schepers <schepers@w3.org>
Cc: Charles Pritchard <chuck@jumis.com>, www-svg <www-svg@w3.org>
On Mon, May 9, 2011 at 5:48 PM, Doug Schepers <schepers@w3.org> wrote:

> But I have heard repeatedly from different browser vendors that until we
> start seeing even more use of SVG by content creators, they are unlikely to
> prioritize improving SVG support; we still have performance problems, and we
> still haven't seen SVG in Chrome on Android.  It's a Catch-22.

Just FYI: the Android built-in browser is not Chrome. It's barely related
beyond the fact they both use Webkit ... and different versions of Webkit,
at that.

You should get real data about why Web devs aren't using SVG as much as
you'd like. I don't believe it's because they're missing advanced features
like many proposed in this thread. Are people really trying to use SVG and
then giving up because it doesn't have non-scaling stroke, or fancier

My instincts are similar to Patrick's --- I'd invest in integration,
performance and education. The one thing he said that I'd take issue with is
"If ..., SVG will be relegated to a vector graphic documents interchange
format". Hey, being *the* vector graphics document interchange format for
the Web isn't too bad!

BTW I can assure you that Mozilla people are working on improving our SVG

"Now the Bereans were of more noble character than the Thessalonians, for
they received the message with great eagerness and examined the Scriptures
every day to see if what Paul said was true." [Acts 17:11]
Received on Tuesday, 10 May 2011 10:07:45 UTC

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