Add support for placeholder text

[KhodorAmmar]

Adds a new default options "placeholder".
Adding a placeholder will add a data-placeholder attribute on the contenteditable area.
Using css's :empty show and hide the "placeholder" text on the content area.

[KhodorAmmar]

Closes #136

[lougreenwood]

Any movement on this PR? looks like an excellent addition @jaredreich?

[pleerock]

• 1

[lougreenwood]

@jaredreich any news on this PR? Looks mighty useful for the community - perhaps you have some concerns which @KhodorAmmar can address?

[KhodorAmmar]

I can see a conflict in the demo.html now, but i can update if the maintainer is happy with the edits

[Duder-onomy]

@jaredreich FWIW, I am using @KhodorAmmar's code in a fork in production right now.
The placeholder support works well.

[EamonNerbonne]

Hmm, as the linked #174 shows, it's not necessarily the case that "conceptually blank" maps very well to css :empty. This PR would kind of require that that mapping stay supported in the future, to avoid breaking changes.

Wouldn't a better alternative be for pell to set some marker class conceptuallyEmpty or whatever, and let people style that? That way, you're not dependant on potentially invisible markup differences in determining whether to show the placeholder; and it also means that if in the future you want to start with a top-level <p> or whatever - you can.

Possibly even simpler to implement and reason about, and potentially good enough for a placeholder might be a concept hasNeverContainedContent which you only ever set to false (i.e. give up on re-showing the placeholder if the user explicitly makes the editable area empty).

[ghaiat]

Hello , any chance this gets merged anytime soon ?

[patzila]

+1

I would also like this to get merged

[jaredreich]

Apologies to everyone waiting for this. I'm planning to give pell some love very soon.

[RossMWoods]

I was looking for a program that produced skinny html and Pell is the best I have found so far.

Here are my reasons:

1. Easy to install. Just copy the folder and create a desktop link to demo.html. (Most of the competitors have complicated instructions and plugins.)
2. Skinny html is simple, clean code.
3. I just copy stuff in and format it with buttons, and immediately get a section of skinny html that I can copy and paste elsewhere.

The future:

1. I can't see the need for the "text" output box.
2. Some things could shrink even more but adding features will grow it.
3. I'd like to see the features equal those of tinymce and its plugins, and most of those form Trumbowyg, including copy and paste from other file types. I'd also like to see a simple head and /head added with a save file option.
4. I wonder if there will be two versions: one simply to generate html files (as I need), and one to be used in online forms like tinymce.

[antony]

I'm also in favour of this

[simonfranzen]

Code works as expected! Good job! Please merge someone :D

[ryansully]

This sounds great! When can this be merged?

[leonetti]

Would love this to be merged!

[mcat-ee]

@jaredreich is there a timeline on resolving this?

[VaelVictus]

Does anyone know if it's possible to fork Pell and then pull some of these requests in? I think our god has abandoned us.

[antony]

yeah you can just do it and maintain your own fork

…

On Tue, 30 Nov 2021 at 02:37, VaelVictus ***@***.***> wrote: Does anyone know if it's possible to fork Pell and then pull some of these requests in? I think our god has abandoned us. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#140 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABVORO4HJWTI6XFZZUN5VLUOQ2FLANCNFSM4FGS2N4Q> .

--

________________________________ ꜽ . antony jones . http://www.enzy.org