sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [flutter_svg] accept "viewBox" or "viewbox" in vector_graphics_compiler.
Labels: package,P3,p: flutter_svg

_Imported from https://github.com/dnfield/flutter_svg/issues/1043_

Original report by @higaski on Feb 25, 2024

I keep getting `Bad state: SVG did not specify dimensions` errors when using the SVG attached here and I can't wrap my head around why? The SVG clearly contains all the 3 attributes the error message is complaining about?

This is the error in detail
```sh
Bad state: SVG did not specify dimensions

The SVG library looks for a `viewBox` or `width` and `height` attribute to determine the viewport boundary of the SVG.  Note that these attributes, as with all SVG attributes, are case sensitive.
```

And this is the beginning of the SVG data
```xml
<svg
   width="271.099mm"
   height="155.14697mm"
   viewBox="0 0 271.099 155.14699"
   version="1.1"
   ...
```


![logo_bricks](https://github.com/dnfield/flutter_svg/assets/13762516/91d665eb-1bc2-4789-9594-f355a656a512)


---
Comment by @LucaCoduriV on Mar 3, 2024
same for me

---
Comment by @rajrushilmakkar on Mar 7, 2024
facing the same issue with this svg
![Social-Emotional-Learning](https://github.com/dnfield/flutter_svg/assets/56961633/1dbd9019-934a-44ab-90bb-1e5872baf27a)


---
Comment by @dnfield on Mar 7, 2024
> facing the same issue with this svg

viewBox is case sensitive. Maybe I should lighten this up though since browsers seem to.

---
Comment by @dnfield on Mar 7, 2024
@higaski your example has a couple pattern elements in it that are using not well supported features for this package, and also includes JavaScript which will never work with this package.

It _is_ a bug that we're requiring a `viewBox` on a `pattern` that has no `width` or `height`, but fixing that won't fix your SVG unfortunately.

---
Comment by @rajrushilmakkar on Mar 7, 2024
 > viewBox is case sensitive.
 
Hi, thanks, changing to viewBox did fix my issue

>  Maybe I should lighten this up though since browsers seem to.

I think that would be nice. Happy to create a PR @dnfield
Repository: flutter
Issue: [flutter_svg] State what SVG version is supported in README
Labels: package,P3,p: flutter_svg

_Imported from https://github.com/dnfield/flutter_svg/issues/1052_

Original report by @gisborne on Mar 29, 2024

I’ve looked at the README and perused the docs. I still have no idea if this supports SVG 1.1, 2, Tiny, SVGT, SVGB or what.
Repository: flutter
Issue: [flutter_svg] Rendering wrong when upgrading from flutter_svg 1.1.6 to 2.0.0 and later
Labels: package,P3,p: flutter_svg

_Imported from https://github.com/dnfield/flutter_svg/issues/1053_

Original report by @quanghd96 on Apr 1, 2024

Rendering wrong when upgrading from flutter_svg 1.1.6 to 2.0.0 and later. So can not use camera to read it. Can you check it?
- 2.0.0 and later
![image](https://github.com/dnfield/flutter_svg/assets/15941383/c7edb219-fba5-4d4a-acb7-07da38277d54)
- 1.1.6
![image](https://github.com/dnfield/flutter_svg/assets/15941383/67f1f300-72fe-4394-a8e0-7deeb6928d3c)
- Origin
![pairingqr (1)](https://github.com/dnfield/flutter_svg/assets/15941383/6c14ce07-d603-40ff-8d53-8ba36e3dfc6e)
Repository: flutter
Issue: [flutter_svg] Rendering problem: Text overlapping
Labels: package,P3,p: flutter_svg

_Imported from https://github.com/dnfield/flutter_svg/issues/1055_

Original report by @IDIM-CGN on Apr 4, 2024

Hi, 

I am using the latest version of flutter_svg (2.0.10+1) and was building it on Android.

The used vector image is displayed correctly in commonly used viewers (e.g. Firefox) but is rendered disrupted inside the app widget:
![grafik](https://github.com/dnfield/flutter_svg/assets/157128615/01f4131a-0564-43a1-96a8-d24e784561f1)

Mainly the texts is overlapping (e.g. "Score" in the title). SVG was exported with the recommended values (see flutter_svg readme).
Also trying to convert svg to a more flat format with svg cleaner - but no success. I would be very happy about any tips!

Thanks!

SVG-File:
![aspergillosis_en-presattrib](https://github.com/dnfield/flutter_svg/assets/157128615/0f0f8c70-e2c3-4069-8867-1064000aec08)
Repository: flutter
Issue: [flutter_svg] SVG filter spec not supported.
Labels: package,P3,p: flutter_svg

_Imported from https://github.com/dnfield/flutter_svg/issues/1058_

Original report by @modulovalue on Apr 17, 2024

Hello Dan,

Consider the following SVG:

![invoice_detail_gradient](https://github.com/dnfield/flutter_svg/assets/24444584/914a765d-f8b8-4697-b96f-ca4b8ace0165)

which appears to be rendered incorrectly by flutter_svg.

Here's what I'm seeing in a Flutter App:

<img width="272" alt="actual" src="https://github.com/dnfield/flutter_svg/assets/24444584/15f729d2-717e-4bf3-b522-187ac279e46e">

Here's what I was expecting:

![expected](https://github.com/dnfield/flutter_svg/assets/24444584/909c913b-3520-4ed3-86f4-43c1f8dfddf6)

Notice how some of the gradients appear to be wrong.

The file was designed in Figma and exported from Figma.

I'm using the following to load that SVG:

```dart
... SvgPicture.asset(path_to_asset) ...
```

With the following flutter release:

```
Flutter 3.16.7 • channel stable • https://github.com/flutter/flutter.git
Framework • revision ef1af02aea (3 months ago) • 2024-01-11 15:19:26 -0600
Engine • revision 4a585b7929
Tools • Dart 3.2.4 • DevTools 2.28.5
```

And the newest flutter_svg release:

```
  flutter_svg: ^2.0.10+1
```

Do you know if there are any limitations that might make this unlikely to ever be fixed or could this be an actual bug?

---
Comment by @sketchitbiz on May 25, 2024
me .. too is there any updates? 

---
Comment by @modulovalue on May 25, 2024
I ended up using PNGs instead.

---
Comment by @jonahwilliams on May 28, 2024
The SVG filter spec isn't supported in the package.

---
Comment by @nbetsaif on Jun 30, 2024
same issue
Repository: flutter
Issue: [flutter_svg] [BUG] Caching is not working correctly.
Labels: package,P3,p: flutter_svg

_Imported from https://github.com/dnfield/flutter_svg/issues/1074_

Original report by @darkstarx on May 30, 2024

You use `SvgCacheKey` that has `keyData` which is `SvgNetworkLoader`.
1. Implement `operator==` and `hashCode` for ColorMapper (actually there is only `TestColorMapper` yet).
2. Fix calculating `hashCode` and comparing the `SvgNetworkLoader.headers` which is `Map<String, String>`.
```dart
  @override
  int get hashCode => Object.hash(url, headers /* HERE */, theme, colorMapper);

  @override
  bool operator ==(Object other) {
    return other is SvgNetworkLoader &&
        other.url == url &&
        other.headers == headers &&  // You NEVER get here true until these are identical maps.
        other.theme == theme &&
        other.colorMapper == colorMapper;
  }
```

It's hardly ever to be happend when user writes the same Map of headers on different pages, usually these are different maps with the same entries.

You have two options:
1. Use `const MapEquality().equals(headers, other.headers)` in the `operator==` and `Object.hashAll([ ...headers.keys, headers.values, ... ])` in the `hashCode` getter.
2. Remove headers from `hashCode` and `operator==` since `headers` don't define the the source of svg data like `url` does.
Repository: godot
Issue: Modifying a node when using inherited scenes causes warning about vanishing
Labels: discussion,topic:editor

### Tested versions

- Reproducible in v4.3.stable.mono.official [77dcf97d8]

### System information

M2 macOS - Sonoma 14.6.1

### Issue description

Repro:
- Download the minimal repro
- Open `base.tscn`
- Right-click the `CanvasGroup` and make it the scene root
- Run the project

It will output this warning:

```
W 0:00:00:0715   instantiate: Node './Label' was modified from inside an instance, but it has vanished.
  <C++ Source>   scene/resources/packed_scene.cpp:254 @ instantiate()
```

What's unusual is that Godot will actually fix¹ the underlying `derived.tscn` file, but only if you open `derived.tscn` in Godot first, otherwise the warning will print every time you run. This is part of why this issue was so insidious for me in particular—I only ever run from VSCode, and it doesn't fix the `tscn` file when you do that.

Here are some expectations I have around this behavior:

- The warning would tell me more information about why this is happening and how to fix it
- I wouldn't need to open the scene file in Godot for it to be changed
- If the file _is_ going to be changed, I think I'd want to be aware of what's changing

Note: I don't know exactly whether I would expect the file to be changed or unchanged; it's hard to know what _should_ happen here. 🤔

¹By "fix", I mean it will remove these lines from `derived.tscn`:

```
[node name="Label" parent="." index="0"]
visible = true
```

### Minimal reproduction project (MRP)

[vanishednoderepro.zip](https://github.com/user-attachments/files/17737443/vanishednoderepro.zip)
Repository: flutter
Issue: [flutter_svg] some 'style' attribute will cause the svg file to fail to render.
Labels: package,P3,p: flutter_svg

_Imported from https://github.com/dnfield/flutter_svg/issues/1077_

Original report by @xyqjay on Jun 11, 2024

1. With the `style` attribute, it can be rendered
```
<svg width="16" height="16" viewBox="0 0 16 16" fill="none" xmlns="http://www.w3.org/2000/svg">
<g id="icon/file">
<path id="Vector (Stroke)" fill-rule="evenodd" clip-rule="evenodd" d="M0.666992 1.66667C0.666992 1.29848 0.965469 1 1.33366 1H14.667C15.0352 1 15.3337 1.29848 15.3337 1.66667V14.0573C15.3337 14.1046 15.3287 14.1507 15.3194 14.1952C15.3288 14.2398 15.3337 14.286 15.3337 14.3333C15.3337 14.7015 15.0352 15 14.667 15H4.33886C3.97067 15 3.67219 14.7015 3.67219 14.3333C3.67219 13.9651 3.97067 13.6667 4.33886 13.6667H14.0003V6.33333H2.00033V10.0573C2.00033 10.4255 1.70185 10.724 1.33366 10.724C0.965469 10.724 0.666992 10.4255 0.666992 10.0573V1.66667ZM2.00033 5V2.33333H14.0003V5H2.00033ZM2.66699 3.66553C2.66699 3.29734 2.96547 2.99887 3.33366 2.99887H3.66699C4.03518 2.99887 4.33366 3.29734 4.33366 3.66553C4.33366 4.03372 4.03518 4.3322 3.66699 4.3322H3.33366C2.96547 4.3322 2.66699 4.03372 2.66699 3.66553ZM5.00033 3.66667C5.00033 3.29848 5.2988 3 5.66699 3H12.667C13.0352 3 13.3337 3.29848 13.3337 3.66667C13.3337 4.03486 13.0352 4.33333 12.667 4.33333H5.66699C5.2988 4.33333 5.00033 4.03486 5.00033 3.66667ZM9.79538 8.52821C10.0534 8.27056 10.4706 8.26808 10.7318 8.52264L12.2253 9.97864C12.4889 10.2357 12.4943 10.6577 12.2373 10.9214C11.9802 11.185 11.5582 11.1904 11.2945 10.9334L10.272 9.93648L8.05631 12.1485C7.79987 12.4045 7.3859 12.4088 7.12419 12.1582L5.40469 10.5115L1.80747 14.1457C1.54845 14.4074 1.12635 14.4095 0.864672 14.1505C0.602994 13.8915 0.600835 13.4694 0.859849 13.2077L4.91838 9.10745C5.17438 8.84882 5.59048 8.84325 5.8533 9.09495L7.5756 10.7443L9.79538 8.52821Z" fill="white" style="fill:white;fill-opacity:1;"/>
</g>
</svg>
```

2.  With the `style` attribute, it can't be rendered!!! (It can be render by Chrome or Edge or Mac's Preview)
```
<svg width="13" height="12" viewBox="0 0 13 12" fill="none" xmlns="http://www.w3.org/2000/svg">
<g id="icon">
<path id="Vector" d="M9 4.5L6.5 7.5L4 4.5H9Z" fill="#888888" stroke="#888888" style="fill:#888888;fill:color(display-p3 0.4784 0.4941 0.5294);fill-opacity:1;stroke:#888888;stroke:color(display-p3 0.4784 0.4941 0.5294);stroke-opacity:1;" stroke-linejoin="round"/>
</g>
</svg>
```
2.1  Delete the `style` attribute  in 2 ,  it can be rendered
```
<svg width="13" height="12" viewBox="0 0 13 12" fill="none" xmlns="http://www.w3.org/2000/svg">
<g id="icon">
<path id="Vector" d="M9 4.5L6.5 7.5L4 4.5H9Z" fill="#888888" stroke="#888888" stroke-linejoin="round"/>
</g>
</svg>
```
Repository: flutter
Issue: [flutter_svg] SVG showing Black bacground when rendered
Labels: package,P3,p: flutter_svg

_Imported from https://github.com/dnfield/flutter_svg/issues/1083_

Original report by @manandharsudhir on Jun 24, 2024

![otp](https://github.com/dnfield/flutter_svg/assets/33796281/a369faaa-de04-44a1-ac4e-5e88259035c1)
Above I have provided the SVG also maximum SVG that I download from Figma doesnt seem to work in Flutter 

I am using 
flutter_svg: ^2.0.10+1
dart: 3.4.1
flutter: 3.22.1

Here is the code:

`SvgPicture.asset("assets/svg/otp.svg"),`

---
Comment by @yargm on Jul 18, 2024
same issue here
Repository: flutter
Issue: [flutter_svg] Error found in FirebaseCrashlytics
Labels: package,p: flutter_svg

_Imported from https://github.com/dnfield/flutter_svg/issues/1085_

Original report by @suhailpatel49 on Jun 26, 2024

I am facing this similar issue [660](https://github.com/dnfield/flutter_svg/issues/660). We are using a third party api and displaying svgs from there so there is no way for us to fix the svgs. Is there any way we can catch the exceptions from the library itself or tell the library to ignore the errors?
Repository: flutter
Issue: [flutter_svg] Can't rotate svg
Labels: package,P3,p: flutter_svg

_Imported from https://github.com/dnfield/flutter_svg/issues/1091_

Original report by @erperejildo on Jul 30, 2024

I have this svg:
```
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- Uploaded to: SVG Repo, www.svgrepo.com, Generator: SVG Repo Mixer Tools -->
<svg fill="#000000" height="800px" width="800px" version="1.1" id="Capa_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"
	 viewBox="0 0 44 44" xml:space="preserve">
<path d="M22,44c-3.309,0-6-2.665-6-5.941V28H5.941C2.665,28,0,25.309,0,22s2.665-6,5.941-6H16V5.941C16,2.665,18.691,0,22,0
	s6,2.665,6,5.941V16h10.059C41.335,16,44,18.691,44,22s-2.665,6-5.941,6H28v10.059C28,41.335,25.309,44,22,44z M5.941,18
	C3.805,18,2,19.832,2,22s1.805,4,3.941,4H18v12.059C18,40.195,19.832,42,22,42s4-1.805,4-3.941V26h12.059C40.195,26,42,24.168,42,22
	s-1.805-4-3.941-4H26V5.941C26,3.805,24.168,2,22,2s-4,1.805-4,3.941V18H5.941z"/>
</svg>
```

And I edited it rotating it 45 degrees looking now like this:

```
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">

<!-- Uploaded to: SVG Repo, www.svgrepo.com, Transformed by: SVG Repo Mixer Tools -->
<svg fill="#000000" height="800px" width="800px" version="1.1" id="Capa_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" viewBox="0 0 44 44" xml:space="preserve" transform="rotate(45)">

<g id="SVGRepo_bgCarrier" stroke-width="0"/>

<g id="SVGRepo_tracerCarrier" stroke-linecap="round" stroke-linejoin="round"/>

<g id="SVGRepo_iconCarrier"> <path d="M22,44c-3.309,0-6-2.665-6-5.941V28H5.941C2.665,28,0,25.309,0,22s2.665-6,5.941-6H16V5.941C16,2.665,18.691,0,22,0 s6,2.665,6,5.941V16h10.059C41.335,16,44,18.691,44,22s-2.665,6-5.941,6H28v10.059C28,41.335,25.309,44,22,44z M5.941,18 C3.805,18,2,19.832,2,22s1.805,4,3.941,4H18v12.059C18,40.195,19.832,42,22,42s4-1.805,4-3.941V26h12.059C40.195,26,42,24.168,42,22 s-1.805-4-3.941-4H26V5.941C26,3.805,24.168,2,22,2s-4,1.805-4,3.941V18H5.941z"/> </g>

</svg>
```

I'm using this page to check and both seem correct.

![addition](https://github.com/user-attachments/assets/a74de1bd-8111-4d1a-834b-9d698c2ddc8e)
![multiplication](https://github.com/user-attachments/assets/692346ff-5e86-43e1-850d-77ce88442e88)
Repository: flutter
Issue: [flutter_svg] SVG produced by verovio doesn't work
Labels: package,P3,p: flutter_svg

_Imported from https://github.com/dnfield/flutter_svg/issues/1092_

Original report by @mkanada on Aug 2, 2024

A simple SVG produced by Verovio Music Notation Engraving Library doesn't work.
![output](https://github.com/user-attachments/assets/6857c49b-dc71-43bb-9362-0ffa02b38991)
Repository: flutter
Issue: [flutter_svg] Add colorMapper argument to named SvgPicture constructors
Labels: package,P2,p: flutter_svg

_Imported from https://github.com/dnfield/flutter_svg/issues/1095_

Original report by @Joshix-1 on Aug 12, 2024

in #856 you mentioned that people should use ColorMapper and that was exactly what I wanted anyway. But as the named constructors do not have a colorMapper argument, I didn't know it existed as an option. The argument could be passed through to the SvgLoader which then could use it. That would be more convinient than having to use the unnamed constructor with the correct BytesLoader.

---
Comment by @Add00w on Sep 1, 2024
The answer is in the same issue [comment](https://github.com/dnfield/flutter_svg/issues/856#issuecomment-1549320661)

---
Comment by @Joshix-1 on Sep 1, 2024
I know how to use ColorMapper. That's not the issue. I want to use the named SvgPicture constructors and use ColorMapper.

---
Comment by @Ali1Ammar on Oct 16, 2024
currently to use ColorMapper , we need to use the loader directly  (SvgAssetLoader/SvgFileLoader/SvgStringLoader/SvgBytesLoader classes) , and we can not use it with SvgPicture
which make it harder to use
Repository: flutter
Issue: [flutter_svg] Failed to display svg with a mask attribute on Flutter 3.24
Labels: package,P2,p: flutter_svg

_Imported from https://github.com/dnfield/flutter_svg/issues/1096_

Original report by @WeiCongcong on Aug 13, 2024

With the latest version flutter and flutter_svg, svg with a `mask` attribute could not be displayed.
For example: [us_flag](https://github.com/HatScripts/circle-flags/blob/gh-pages/flags/us.svg) could not be displayed. But if the mask attribute is removed (the shape will be changed), it could be displayed.
Repository: flutter
Issue: [flutter_svg] Aspect ratio of container is not maintained when FittedBox is at play
Labels: package,P2,p: flutter_svg

_Imported from https://github.com/dnfield/flutter_svg/issues/1098_

Original report by @Ortes on Aug 19, 2024

When FlutterSvg is used with `contain` or `fitWidth` visually the svg is correctly fitted like the option but the container does not keep the aspect ratio of the svg.
For example if the SvgPicture is contained in a Container with a background the background is visible outside of the svg boundary.
Here is an illustration:
![2024-08-19-141309_319x873_scrot](https://github.com/user-attachments/assets/6667d6c5-ee7d-42c6-84c4-e7b529b71718)

Code:
``` dart
Container(
  width: 300,
  color: Colors.green,
  child: SvgPicture.asset(
    'assets/background/svg/pattern-single.svg',
    fit: BoxFit.fitWidth,
  ),
),
```

In this example my svg is 768x821 and I it is contained in a 300 width container as we can see the svg in the center look correct but the container is still 821 pixel tall which makes my background overflow above and bellow the svg. Would it be nicer if the container resized the same way ?

I have found 2 workaround:
``` dart
Container(
  width: 300,
  color: Colors.green,
  child: AspectRatio(
    aspectRatio: 768 / 821,
    child: SvgPicture.asset(
      'assets/background/svg/pattern-single.svg',
    ),
  ),
),
```

In this one you have to manually fill the pixel size of the image.

``` dart
Container(
  width: 300,
  color: Colors.green,
  child: FittedBox(
    child: SvgPicture.asset(
      'assets/background/svg/pattern-single.svg',
    ),
  ),
),
```

This one works fine but I suppose you already use FittedBox in your code that is weird to use 2 nested Fittedbox Right ?
Repository: flutter
Issue: package tool_format check should output diff
Labels: team,package,c: proposal,team-ecosystem,P2,triaged-ecosystem

The packages repo tool format says which files require formatting.  It would be helpful if it also printed the patch diff like the other format command does.

https://github.com/flutter/packages/blob/26e123a6ce039da6b75fe4248e93c8aeeb6d395b/script/tool/lib/src/format_command.dart#L196-L198


Current `tool_format` output:

```

Formatted lib/src/drive_examples_command.dart
Formatted test/drive_examples_command_test.dart
Formatted 94 files (2 changed) in 3.10 seconds.
```

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8731414599540111569/+/u/Run_package_tests/tool_format/stdout
Repository: node
Issue: Expose the "enhanced" stack trace from uncaught exceptions to the `uncaughtException` and `uncaughtExceptionMonitor` handlers on `process`
Labels: events,feature request

### What is the problem this feature will solve?

In my app, I have a logging system which writes entries to files and/or the network in a machine-parsable form. I use the `uncaughtException` handler on `process` in order to get uncaught exceptions written out to this logging system. I noticed that if there's no `uncaughtException` handler, Node will print out an extra stack trace to the console indicating the call site of the `<emitter>.emit('error', ...)` call which emitted the ultimately-uncaught exception. However, it seems like there's no programmatic way for me to get that extra trace in my own handler.

This feature will solve the problem of being able to programmatically extract this extra — and quite useful! — information in a way that works well with a system that eschews the console.


### What is the feature you are proposing to solve the problem?

I don't know what tactic would work best within the larger Node ecosystem, but as a straw-man suggestion:

Add a third argument to the `uncaughtException` and `uncaughtExceptionMonitor` callbacks when an "enhanced" error is available, containing information corresponding to the site and target of the `emit()` call. It could, for example, be a plain object containing an `Error` representing the call site and an object reference to the emitter itself. But if that's too dangerous, it might instead have strings representing that info. For example (in the former case), the following would nearly duplicate what the current default `uncaughtException` handler prints out to the console:

```js
process.on('uncaughtException', (err, origin, emitInfo) => {
  console.log('%s', err.stack);
  if (emitInfo) {
    const { emitter, emitSite } = emitInfo;
    console.log(`Emitted 'error' event of ${emitter.constructor.name} instance at:\n%s`,
      emitSite.stack);
  }
});
```


### What alternatives have you considered?

Having a separate process to scrape console output to find things that look like uncaught exceptions, so I can push them into the structured logging system. (Oof.)
Repository: flutter
Issue: [vector_graphics] Optimize: clips
Labels: package,team-engine,p: vector_graphics

_Imported from https://github.com/dnfield/vector_graphics/issues/21_

Original report by @dnfield on Mar 24, 2022

We should be able to pre-process clips such that we do not require any clipping at runtime.

For example, use path intersection logic to produce a path or set of paths that fit within the clipped area.

---
Comment by @dnfield on Apr 12, 2022
This has to take into account stroking properties altering the effective size of the path. For example, a path with a stroke width that != 1 or a non-butt cap will draw additional pixels that should be clipped. 

For instance, the following relatively simple SVG cannot be clipped without tessellating the stroke into a fill (or at least into vertices):

```svg
<svg width="10" height="10">
  <clipPath id="clip0">
    <path d="M2 3h7.9v2H1" />
  </clipPath>
  <path d="M2, 5L8,6" stroke="black" stroke-linecap="round" stroke-width="2" clip-path="url(#clip0)" />
</svg>
```
Repository: flutter
Issue: [vector_graphics] Optimize overdraw
Labels: package,team-engine,p: vector_graphics

_Imported from https://github.com/dnfield/vector_graphics/issues/23_

Original report by @dnfield on Mar 24, 2022

We should be able to eliminate overdraw. This will also require that we pre-calculate blends especially for overlapping transparent shapes. This will mean we can eliminate saveLayers related to group/overlapping opacity.