5 ms·
I note that (at least in the playground example) there's zero attention paid to accessibility (e.g. how would someone know the "bold" button is the "bold" butto
by Tloewald 10y ago
I note that (at least in the playground example) there's zero attention paid to accessibility (e.g. how would someone know the "bold" button is the "bold" button?).
Also (and kind of related) is there an option that is completely free of UI implementation (outside the editable region)? Almost any project will have its own UI libraries and foibles, and I don't think it's a good idea to force your own UI library into the mix.
- jhchen 10y agoThe playground favors very short code for experimentation, given the limited screen real estate for the split view. Quill could do better in the accessibility front though and autofill titles and aria attributes for you. However at the moment you would have to create an HTML element with the aria attributes and pass that into the toolbar[1]. Please feel free to open a feature request for tracking. You can also use Quill without either of its themes or any of its UI by just using quill.core.js and quill.core.css[2]. The Cloning Medium with Parchment guide[3] in fact starts with this and builds custom UI on top of quill.core.js/quill.core.css. [1] http://quilljs.com/docs/modules/toolbar/#container http://quilljs.com/docs/modules/toolbar/#container [2] http://quilljs.com/docs/download/ http://quilljs.com/docs/download/ [3] http://quilljs.com/guides/cloning-medium-with-parchment/ http://quilljs.com/guides/cloning-medium-with-parchment/
- Tloewald 10y agoThanks for your reply. I think the quill.core.js option addresses both of these issues.