
I know they are locate in /assets/
https://github.com/quilljs/quill/tree/develop/assets/icons
.svg and use it anywhere I want.jpg) PNG (.png)Any solution?
Thank you!
I asked you before to not include screenshot if it's not required. We all know how the Quill icons look.
Github issues are for bugs. Please ask general questions like this on StackOverflow.
@benbro
I disagree with you on screenshot part.
screenshot make it more clear, human are visual animal.
people these day don't have patience to read text, they just want image to get to the point
I am not sure why you hate screenshot so much. what's the big deal?
in this issue and last issue https://github.com/quilljs/quill/issues/2276
screenshot make what I want express more clearly
it's not like 30 big image that make reader scroll endlessly.
I would ask this in StackOverflow.
and I would post only bug-relate issue from now on.
thanks
Update: it's been solved. thanks to martinstoeckli and ccprog
@benbro
Github issues are for bugs.
Question: If I want propose something new, can I post them in Github issue?
For example. I want add new example CodePen into Quill Playground,
or I want write a new page for Quill Doc,
it seem reasonable to post into issue. I don't want "harass" @jhchen on Twitter
post on StackOverflow would get a lot downvote and not helpful for people there.
I don't want spend couple hours writing PR and get rejected.
a issue discuss about new PR would help save time on both side
Most helpful comment
@benbro
Question: If I want propose something new, can I post them in Github issue?
For example. I want add new example CodePen into Quill Playground,
or I want write a new page for Quill Doc,
it seem reasonable to post into issue. I don't want "harass" @jhchen on Twitter
post on StackOverflow would get a lot downvote and not helpful for people there.
Why I want ask first, then act?
I don't want spend couple hours writing PR and get rejected.
a issue discuss about new PR would help save time on both side