Option to disable placeholders about medium-editor

[jarlg]

How would you like this to be implemented? Could add a simple data-disable-placeholders='true', what do you think of that?

I think currently the placeholders aren't very nice. I am working a bit on implementing "templates" where you set some default elements (ex: h3, h4 and p) within your .editable and interpret these as a template, and each of the elements has a placeholder. This conflicts with current placeholders, and I would need to make something like data-disable-placeholders='true' and data-enable-templates='true'. I don't think that's really nice. A solution would be to not have placeholders enabled by default, but something like the user manually adds the element to .medium-editor-placeholder.

I have made a suggestion here: jarlg/Medium-Editor@dc12d1783fd94332ff99a6d92a01e9ca04baaf9b and another commit (child of this one) that fixes some styling issues, but that might be just on my side.

Vaguely related:
Also, I've been wondering a bit about that "boundaries" of this project. Currently it says in the readme it is a clone of the medium toolbar, in which case I don't think placeholders/markdown should be implemented at all actually. However, the project is called Medium-Editor and in that context it makes more sense. What do you think, @daviferreira?

[daviferreira]

I think it should follow the disable-return and disable-toolbar pattern, with a global and a per element option to disable the placeholders. But I'm also not happy with current placeholders. I think perhaps they should be elements instead of pseudo elements for better styling and manipulation.

Well, it's not about the toolbar anymore, I think it never was since we have implemented contenteditable. I think the foucs should be on manipulating selected texts/elements. What I don't want to do is: image action, tables etc.

[nmielnik]

This is now supported via 'disablePlaceholders', though there isn't a data-disable-placeholder that can make the same functionality work...If we still want this, we should open a new issue.