Rendering an SVG file to an ImageSkia

[Nicholas Bishop]

Hi,

Is there any existing way to load an SVG file and render it into a
gfx::ImageSkia?

Thanks,
-Nicholas

[Stephen Chenney]

Context please. In general, the SVG content will not end up in a rastered image until rasterization on the GPU. You would need to intercept the painting command stream and paint into the gfx object. Maybe the canvas APIs do something similar already but I doubt the destination type is the same.

Stephen.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
    http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAB0M8MkwGvWJOrjj0W3qxH38km_0xeDtm0VOhHuxp%3DFNVvtH%2Bw%40mail.gmail.com.

[Nicholas Bishop]

Context: I'm trying to render an SVG icon file into an image for use
as an icon in the Chromium OS UI. The input files aren't known until
runtime, so I can't just pre-render them.

[Peter Kasting]

On Fri, Mar 2, 2018 at 2:06 PM, Nicholas Bishop <nbi...@neverware.com> wrote:

Context: I'm trying to render an SVG icon file into an image for use
as an icon in the Chromium OS UI. The input files aren't known until
runtime, so I can't just pre-render them.

We do something like this in chrome/browser/bitmap_fetcher/ : get image data from the network, decode it, and send it to consumers as Skia objects.

This in turn is built atop chrome/browser/image_decoder.h, which is a way of safely decoding image data inside a sandbox.

All that said, if you give even more context about what's going on here, I might have better suggestions.  Why SVG, for example, and where are the images coming from/what part of the UI are they for?

PK

[PhistucK]

Not exactly this, but maybe halfway -

http://evanstade.github.io/skiafy/

(Context - https://chromium.googlesource.com/chromium/src/+/master/components/vector_icons/README.md)

☆PhistucK

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
    http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+unsubscribe@chromium.org.

[Dominick Ng]

We'd like to do something similar for this in order to allow websites to supply SVG icons for progressive web apps (which isn't currently supported in Chrome). This is a fairly commonly requested feature.

When a user adds a site to home screen, we download the icon specified by the site and use it as the home screen icon / shelf icon. We use WebContents::DownloadImage for this, which doesn't support SVG because SVG isn't really an image. We'd need a way of rendering SVG into a Skia object to allow us to support SVG as well for this process.

[Florin Malita]

Skia does have experimental/limited support for SVG rasterization: https://github.com/google/skia/blob/master/experimental/svg/model/SkSVGDOM.h

The API is explicit, but it wouldn't be a huge stretch to package as a supported image decoder and possibly hide behind the SkImage API.

This is not currently built by Chrome, and off the top of my head is missing filters effects, SMIL and text support.

Assuming there is a good use case and interest, we could allocate resources to fill some of the gaps.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/512f3722-8ec1-4e82-9aa6-368f9ee04522%40chromium.org.

[Dominick Ng]

Packaging this into Chrome as a supported image decoder would be a really useful thing for us, especially if it can be feature-compliant with the existing SVG implementation (so developers aren't surprised when their icons don't render right when retrieved via this pipeline). Otherwise, we have no way of supporting SVG icons.

[Florin Malita]

SVG is a beast, and I don't expect Skia's SVG renderer to reach full spec compliance or be on par with Blink's implementation.  If you require all Chrome-supported SVG bells and whistles to also be available for icons, then I believe your only option is to find a way to use Blink's SVG renderer.

If OTOH you can tolerate a well-defined SVG subset (most SVG art uses a small fraction of the spec), then the Skia SVG lib might be an option to consider.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/e4e47702-a953-4854-8864-684ba1cc674a%40chromium.org.

[Alex Danilo]

This is a bug you should star: https://bugs.chromium.org/p/chromium/issues/detail?id=294179

Alex

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CADgYMVee9C-_d2FDu73o8uXn%2BCc2%2BA5ETDhPpwHzGyU1ecy%2BEA%40mail.gmail.com.

[Dominick Ng]

Thanks Florin. For predictability reasons, we would want to try and match Blink's SVG rendering, which probably means we'll need to wait till https://crbug.com/294179 is resolved (thanks Alex).

[Daniel Bratell]

I think warning bells should chime when the best idea is to duplicate existing functionality. When is it ever right to have duplicate functionality in a product? Yet it keeps happening in Chromium.

/Daniel

☆PhistucK

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAB0M8MkwGvWJOrjj0W3qxH38km_0xeDtm0VOhHuxp%3DFNVvtH%2Bw%40mail.gmail.com.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/512f3722-8ec1-4e82-9aa6-368f9ee04522%40chromium.org.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/e4e47702-a953-4854-8864-684ba1cc674a%40chromium.org.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CADgYMVee9C-_d2FDu73o8uXn%2BCc2%2BA5ETDhPpwHzGyU1ecy%2BEA%40mail.gmail.com.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/98de4580-32eb-474d-982b-043f26726ff3%40chromium.org.

--

/* Opera Software, Linköping, Sweden: CET (UTC+1) */

[Jan Tošovský]

> SVG is a beast, and I don't expect Skia's SVG renderer to reach full spec compliance

> or be on par with Blink's implementation.  If you require all Chrome-supported SVG

> bells and whistles to also be available for icons, then I believe your only option is to find

> a way to use Blink's SVG renderer.

I wish Blink's SVG implementation is moved into Skia (kind of optional module) so it could be used upstream without reinventing the wheel. But I understand there are surely lots of technical obstacles.

Currently I consider Flutter for my future mobile app. It will generate complex SVG (filters, masks, text on path). I prefer declarative SVG approach over low level rendering instructions (e.g. text on path would be quite tricky). Flutter use Skia. Flutter doesn't plan to support SVG https://github.com/flutter/flutter/issues/1831 - If Skia would support SVG natively, the Flutter could change mind...

There is SVG plugin for Flutter available https://github.com/dnfield/flutter_svg, but its support is rather basic.

So currently only option in Flutter is to wait for adding the support for kind of WebView https://github.com/flutter/plugins/tree/master/packages/webview_flutter - which is now still experimental. But I expect instantiating the full html renderer is very expensive in terms of CPU/memory.

There is Skia issue related to SVG, but it seems to have low priority https://bugs.chromium.org/p/skia/issues/detail?id=5596

I am big fan of SVG, I am glad it has finally broad browser support, I am glad it is now taken seriously by web designers and even developers, so I expect the demands for SVG libraries will increase significantly in near future.

Just putting my thoughts.