Dmitry Sharabin

> Is there an upcoming new release? 🤔 Yes. The current dev version (the one you are experimenting with) is supposed to be the next `v0.3.0` release.

Here is a couple of examples: https://codepen.io/dmitrysharabin/pen/gOoqOzj

There is an issue I don't know how to address yet: I can't preserve an attribute case. E.g., `mv-attr-veiwBox` is converted to `mv-attr-viewbox`. And it doesn't let us use the...

> I tried to add different attributes with letters in different cases to elements inside and outside a Mavo app, and it looks like browsers convert attributes to lower case...

> Is the casing issue cosmetic or does it actually cause loss of functionality? In the SVG Path Builder we won't be able to get rid of the error caused...

> actually, here is another possible approach: apparently there is a specified list of tag adjustments that you could perform automatically *if the node with the attributes is an svg...

> Why not? Can't we specify `mv-attr-viewBox` and then your code would specify `viewbox` (lowercase), which I think would still work? Ah, yes. You are absolutely right—lowercase attributes are not...

Thanks to David, we know that [browsers adjust SVG attributes that are not all lowercase](https://html.spec.whatwg.org/multipage/parsing.html#adjust-svg-attributes). That means that when there is an expression inside the value of an attribute (e.g.,...

> Are you using the correct namespace for these attributes? I wonder if that's why `viewbox` doesn't work. Hmm. That's a good question. I don't know. I definitely need to...

Here are some results of my research concerning SVG, its elements, attributes, and namespaces: 1. Regardless of whether we use `viewBox` or `viewbox`, the browser adjusts it to `viewBox` (and...