Lev Solntsev

> The attribute is valuable most of the time… While most users > …only work with simple svg stuff… Don't you see a contradiction here? It's impossible to conform everyone....

Perhaps readme should be updated. SVGO mostly optimize without a _visible_ affect on rendering result. One of the most effective optimizations is reducing float numbers precision. Usually, one will not...

> You are wrong, removing the **viewBox affects rendering**. Please read the viewBox documentation on mozilla and check the example, it's the same svg used three times with three different...

Thinking it over, SVGO could use some already known optimizers like pngout and mozjpeg. It could search them in standard places (platform-specific) and some side plugins could add formats and...

Win 7 x64, Chromu, based browser Yandex, different PCs and drivers.

https://browser.yandex.ru/desktop/main/

Yep, SVGO is based on [SAX parser](https://github.com/isaacs/sax-js) which has such issues.

Could be this proposal unified with `@property` rule? So one can define not only properties but their configuration too. Maybe define groups with something like `@property-group` syntax to avoid ambiguity?...

That's a good point. I don't think however, that it should be propagated to auto-magically created groups. Could be a source of funny bugs.

AFAIK, I wrote that plugin and excluded it just for the fact it makes paths longer than rects. Nothing to do with optimization.