Sometimes I'm struggled with the performance and inconsistent behaviour between browsers while using css-doodle. This often leads me to consider switching to other tools.
But I really like the syntax of css-doodle. So maybe I could reimplement it using another render layer other than CSS, like canvas?
@yuanchuan I'm sure you already know this, but you can also combine canvas and svg, by layering divs on top of each other. I'd love to see what you'd do with that.
@kristinHenry Right, the only problem is when I want to export and save the result, a headless browser is needed to take the screenshot programatically.
Is there a better way in SVG to prevent ID collisions among multiple inline SVG elements (e.g. gradients), other than randomizing or adding prefixes to IDs?
@sarajw Ah I see. It's hard to share them right now since the original size of the canvas is 2000x and bigger. I have to ship my tool along with them in order to preview in the browser :D
@yuanchuan It might be worth adding no-JS fallback text to <css-doodle> (something like “enable JavaScript to view demo”). I have JavaScript disabled by default in my desktop browser, and I didn’t even notice that there are inline demos in the article.