Hannes Diercks

The problem is spotify auth goes over a differen API which is not part of their OAS spec. So there's nothing oazapfts (or similar generators) can do about it.

/bump :+1:

I would also rather focus on adding some cypress/e2e tests that ensure that the developer-facing-API works as expected.

hav you tried to use svg rendering? See https://github.com/0xfe/vextab#quick-start > for SVG include RaphaelJS in a script tag before vextab-div.js

sorry, have not worked with this project in a long time. i just remembered that svg worked fine for me when i played around with this.

:+1:

:+1: I'd love that, too!

you could digg yourself through the (not at all documented [ref #34]) [fontsService](https://github.com/Jimdo/angular-fontselect/blob/master/src/js/service.fonts.js) it holds all fonts and all font providers have not tested that but it should work s.th....

we could also refactor the font-provider pattern (see [service.fonts.js#L38-L39](https://github.com/Jimdo/angular-fontselect/blob/master/src/js/service.fonts.js#L38-L39)) and make it truely configurable, allowing you to disable all default providers and add your own

I agree, we've not put much effort in visual flexibility. Currently i don't know any other use cases then the one we're using so i don't have a good starting...